Two instances of Lazarus ( one is dpkg -i and the other is built using make )

[Aruna]

Hi, I recently lost my local repo and all the projects in it when I did a git --reset hard. I decided to start from scratch again downloaded the *.deb files and installed them using:

Code: Pascal  [Select][+][-]

1. sudo dpkg -i fpc-src_3.2.2-210709_amd64.deb
2. sudo dpkg -i fpc-laz_3.2.2-210709_amd64.deb
3. sudo dpkg -i lazarus-project_3.4.0-0_amd64.deb
4.  

everything went well and I see the Lazarus icon under my Applications-->Programming (screenshot attached)] . Now for the life of me, I could not find where dpkg goes and puts everything. I wanted to change the splash_logo to a custom one. But unable to do so because I cannot find the folder.

So I decided to go with @dbanon's method of building everything from the source. This gave me what I wanted. I had access to the files and folder layout where I can browse and read freely. ( screenshot attached)

Now what is curious is this, both instances seem to co-exist peacefully in my Debian system. So far no issues. My questions are:
1. Where does dpkg put everything? Does anyone know?
2. Both installations work. No issues (so far). Has anyone else done this before? If so what was the reason you decided to go this way?

[TRon]

Hi, I recently lost my local repo and all the projects in it when I did a git --reset hard. I decided to start from scratch again downloaded the *.deb files and installed them using:

Sorry for your loss. It happens to the best of us

Now what is curious is this, both instances seem to co-exist peacefully in my Debian system. So far no issues.

Looks can be deceiving 

1. Where does dpkg put everything? Does anyone know?

Never used the .deb packages myself. If I must I use a tarball @ sourceforge.

I prefer not to use anything package-manager related because on the long run you never know what is going to happen.

2. Both installations work. No issues (so far). Has anyone else done this before? If so what was the reason you decided to go this way?

I have multiple FPC' and Lazarus' neatly setup on my system.

The reasons (that I can currently come up with) are:
- I use trunk for testing, that needs to be updated regularly.
- To be able to verify behaviour across different versions
- I prefer my stable development to not immediately jump on the new and shiny. It has a tendency to blind you and hit you in the face unexpectedly. Realize that sometimes there are breaking changes.


The most important part to know about is the fpc.cfg file. Different (installation) solutions scatter them all over the place or except this file to be somewhere specific and so I deny any fpc.cfg except my own (command line options -n and @, see also https://www.freepascal.org/docs-html/user/userap1.html). It prevents headaches.

The same is true for Lazarus though that has better automated accommodation for multiple installations, see also https://wiki.freepascal.org/Multiple_Lazarus

[bpranoto]

1. Where does dpkg put everything? Does anyone know?

Open the deb file with gdebi, and you can see the files in the included file tabs like the screenshot below

[Aruna]

1. Where does dpkg put everything? Does anyone know?

Open the deb file with gdebi, and you can see the files in the included file tabs like the screenshot below

Thank you @bpranoto this worked. For anyone who may be interested the DEB internal file paths are here

EDIT: It puts everything under /usr/share/lazarus/3.4.0

[MarkMLl]

EDIT: It puts everything under /usr/share/lazarus/3.4.0

For future reference, can I please comment the standard apt-file utility. I don't have any Debian FPC packages on my system (because I always build from scratch), but as an example of something that has come from their standard repo:

Code: Text  [Select][+][-]

1. $ apt-file list libqt5pas-dev
2.  
3. libqt5pas-dev: /usr/lib/x86_64-linux-gnu/libQt5Pas.so
4. libqt5pas-dev: /usr/share/doc/libqt5pas-dev/changelog.Debian.gz
5. libqt5pas-dev: /usr/share/doc/libqt5pas-dev/copyright
6. libqt5pas-dev: /usr/share/pascal/qt5/qt5.pas
7.  

And no, I /don't/ know where I got the initial info on that program. It's just something buried deep in the unix subconscious...

MarkMLl

[CharlyTango]

I have multiple FPC' and Lazarus' neatly setup on my system.

me too -- but i use fpcupdeluxe to install Lazarus in any desired combination

[af0815]

I never mix the installation. Only one installation from the system = default installation OR multiple installations side by side without a default installation.

Mixing both can make a lot of headache, because the default installation can be unwanted used in the background, if you make a small mistake in configuring. If it is side by side you see a error and can react, but if the wrong fcl/fpc is used it can make mistorius errors and unwanted results.

[Aruna]

Hi, I recently lost my local repo and all the projects in it when I did a git --reset hard. I decided to start from scratch again downloaded the *.deb files and installed them using:

Sorry for your loss. It happens to the best of us

Thank you TRon it was a real shock when I saw the folder(s) were wiped clean. Ah well, you live and learn :-)

Now what is curious is this, both instances seem to co-exist peacefully in my Debian system. So far no issues.

Looks can be deceiving 

Oh dear 

Never used the .deb packages myself. If I must I use a tarball @ sourceforge.

I usually build from scratch for some reason I can't recall I did not do so this time. (I must start building from scratch, It prevents a whole heap of possible mishaps.)

I prefer not to use anything package-manager related because on the long run you never know what is going to happen.

Me too I stay far away from package managers

I have multiple FPC' and Lazarus' neatly setup on my system.

The reasons (that I can currently come up with) are:
- I use trunk for testing, that needs to be updated regularly.
- To be able to verify behaviour across different versions
- I prefer my stable development to not immediately jump on the new and shiny. It has a tendency to blind you and hit you in the face unexpectedly. Realize that sometimes there are breaking changes.


The most important part to know about is the fpc.cfg file. Different (installation) solutions scatter them all over the place or except this file to be somewhere specific and so I deny any fpc.cfg except my own (command line options -n and @, see also https://www.freepascal.org/docs-html/user/userap1.html). It prevents headaches.

The same is true for Lazarus though that has better automated accommodation for multiple installations, see also https://wiki.freepascal.org/Multiple_Lazarus

  To be able to verify behaviour across different version's sounds interesting to me. I must try this one day. The lazarus cfg file I found a wierd fix when you have multiple versions. You know how Lazarus wants you to specify the primary config path:

Code: Pascal  [Select][+][-]

1. aruna@debian:~/lazarus3/lazarus$ ./lazarus --primary-config-path=~/.lazarus_test

and it starts to hiccup I did this:

Code: Pascal  [Select][+][-]

1. aruna@debian:~/lazarus3/lazarus$ ./lazarus --primary-config-path=

left it empty. Guess what it woiks!~

And this works as well:

Code: Pascal  [Select][+][-]

1. aruna@debian:~/lazarus3/lazarus$ ./lazarus --pcp=

Why does this work? I really do not know, but it works.




 

[Aruna]

EDIT: It puts everything under /usr/share/lazarus/3.4.0

For future reference, can I please comment the standard apt-file utility. I don't have any Debian FPC packages on my system (because I always build from scratch), but as an example of something that has come from their standard repo:

Code: Text  [Select][+][-]

1. $ apt-file list libqt5pas-dev
2.  
3. libqt5pas-dev: /usr/lib/x86_64-linux-gnu/libQt5Pas.so
4. libqt5pas-dev: /usr/share/doc/libqt5pas-dev/changelog.Debian.gz
5. libqt5pas-dev: /usr/share/doc/libqt5pas-dev/copyright
6. libqt5pas-dev: /usr/share/pascal/qt5/qt5.pas
7.  

And no, I /don't/ know where I got the initial info on that program. It's just something buried deep in the unix subconscious...

MarkMLl

Hi @MarkMLI I used dpkg remeber? So apt-file list shows nothing I guess maybe because I never used it? But after some digging around in the man pages I found:

Code: Text  [Select][+][-]

1. dpkg --contents lazarus-project_3.4.0-0_amd64.deb

and that gives you full paths. I tested apt-file list with your example and I got this:

Code: Bash  [Select][+][-]

1. aruna@debian:~/lazarus3$ apt-file list libqt5pas-dev
2. libqt5pas-dev: /usr/lib/x86_64-linux-gnu/libQt5Pas.so
3. libqt5pas-dev: /usr/share/doc/libqt5pas-dev/changelog.Debian.gz
4. libqt5pas-dev: /usr/share/doc/libqt5pas-dev/copyright
5. libqt5pas-dev: /usr/share/pascal/qt5/qt5.pas
6. aruna@debian:~/lazarus3$

When I read 'It's just something buried deep in the unix subconscious..' I immediately thought oh-kay that is another way of saying go look at the man pages, so I did :-)

[TRon]

To be able to verify behaviour across different version's sounds interesting to me. I must try this one day. The lazarus cfg file I found a wierd fix when you have multiple versions. You know how Lazarus wants you to specify the primary config path:

Code: Pascal  [Select][+][-]

1. aruna@debian:~/lazarus3/lazarus$ ./lazarus --primary-config-path=~/.lazarus_test

and it starts to hiccup I did this:

Code: Pascal  [Select][+][-]

1. aruna@debian:~/lazarus3/lazarus$ ./lazarus --primary-config-path=

left it empty. Guess what it woiks!~

And this works as well:

Code: Pascal  [Select][+][-]

1. aruna@debian:~/lazarus3/lazarus$ ./lazarus --pcp=

Why does this work? I really do not know, but it works.

I am not familiar with your current issue but as a guess could it perhaps be that the directory you are referring to in the option does not exist yet ?

[Aruna]

I am not familiar with your current issue but as a guess could it perhaps be that the directory you are referring to in the option does not exist yet ?

I am sorry I did not explain properly. When you start Lazarus with a command line such as ./lazarus without specifying a primary configuration path.
In my case, it gives me the warning shown in the attached screenshot. I hope it is clear now what I did?

So after meddling with it a few times I suddenly realized if I leave the PCP empty then somehow Lazarus builds the cfg. 

[MarkMLl]

I am sorry I did not explain properly. When you start Lazarus with a command line such as ./lazarus without specifying a primary configuration path.
In my case, it gives me the warning shown in the attached screenshot. I hope it is clear now what I did?

So after meddling with it a few times I suddenly realized if I leave the PCP empty then somehow Lazarus builds the cfg.

In that case write a /usr/local/bin/lazarus program that handles the options properly.

Code: Text  [Select][+][-]

1. #!/bin/sh
2.  
3. # set -x
4.  
5. PROGRAM=lazarus
6. VERSION=`basename $0`
7. BINARY="/usr/local/share.lazarus/$VERSION/$PROGRAM"
8. CONFIG="$HOME/.$VERSION"
9.  
10. if [ x$1x = x+qt5x ]; then
11.   BINARY=$BINARY-qt5
12.   shift
13. fi
14.  
15. if [ x$1x = x+gtk2x ]; then
16.   BINARY=$BINARY-gtk2
17.   shift
18. fi
19.  
20. if [ ! -x "$BINARY" ]; then
21.   echo "File $BINARY does not exist or is not executable"
22.   exit 1
23. fi
24.  
25. if [ ! -d "$CONFIG" ]; then
26.   echo "WARNING: configuration directory $CONFIG does not exist"
27. fi
28.  
29. echo $BINARY --pcp=$CONFIG $@
30. exec $BINARY --pcp=$CONFIG $@
31.  

Code: Text  [Select][+][-]

1. 0 1>markMLl@kdg-dev-01:/usr/local/bin$ ls -l lazarus*
2. lrwxrwxrwx 1 root root   32 Feb 20  2024 lazarus -> /usr/local/share.lazarus/lazarus
3. lrwxrwxrwx 1 root staff   7 May 15  2017 lazarus-1.0.14+2.6.4 -> lazarus
4. lrwxrwxrwx 1 root root    7 Mar  4  2017 lazarus-1.6.4+3.0.2 -> lazarus
5. lrwxrwxrwx 1 root staff   7 Jul  3  2018 lazarus-1.8.0+3.0.4 -> lazarus
6. lrwxrwxrwx 1 root staff   7 Jul  3  2018 lazarus-1.8.2+3.0.4 -> lazarus
7. lrwxrwxrwx 1 root staff   7 Jul  3  2018 lazarus-1.8.4+3.0.4 -> lazarus
8. lrwxrwxrwx 1 root root    7 Sep  8  2021 lazarus-2.0.10-2+3.2.0 -> lazarus
9. lrwxrwxrwx 1 root root    7 Nov 21  2020 lazarus-2.0.10+3.2.0 -> lazarus
10. lrwxrwxrwx 1 root root    7 Sep  8  2021 lazarus-2.0.12+3.2.0 -> lazarus
11. lrwxrwxrwx 1 root root    7 Mar 18  2020 lazarus-2.0.6+3.0.4 -> lazarus
12. lrwxrwxrwx 1 root root    7 Nov 19  2020 lazarus-2.0.8+3.0.4 -> lazarus
13. lrwxrwxrwx 1 root root    7 Jan  9  2023 lazarus-2.2.4+3.2.2 -> lazarus
14. lrwxrwxrwx 1 root root    7 Sep  2  2023 lazarus-2.2.6+3.2.2 -> lazarus
15.  

MarkMLl

[MarkMLl]

Hi @MarkMLI I used dpkg remeber? So apt-file list shows nothing I guess maybe because I never used it?

"       -D, --from-deb
           Use contents of the given .deb archives(s) as patterns.  Useful for searching for file conflicts with other packages.  Implies -F.
"

MarkMLl

[TRon]

I am sorry I did not explain properly. When you start Lazarus with a command line such as ./lazarus without specifying a primary configuration path.

Ah, ok. Actually it is my bad (I can see that now).

So after meddling with it a few times I suddenly realized if I leave the PCP empty then somehow Lazarus builds the cfg.

That is the part where things become cloudy.

If you leave the --primary-config-path aka --pcp option (they both have the same meaning) empty then Lazarus will use the default location (whatever Lazarus decided is the default location).

Hence that with multiple installations it becomes more important to explicitly specify this option.

fwiw, there is also a secondary configuration option, but I personally never used it because I make use of more than two Lazarus'.

So, if you leave that option empty on startup then each Lazarus will try and use the same configuration settings. And that happens even when these configuration settings are incompatible, which is the reason for the dialog that was presented (as Lazarus recognizes this situation. That is, things got better over time. Sometimes the configuration files get 'broken' between versions though over time the Lazarus developers tried to solve these issues with for example being able to write projects options in a compatible mode)

Also note that recent versions of Lazarus allow for a lazarus.cfg next to the executable in which you can store that pcp option so that you do not have to provide it on startup (but realize that is a new feature, and older versions of Lazarus might not support that, hence I personally still use the parameter option in order to make things consistent on my setup)

A solution as provided by Mark is also a very good one (and one I use but then for the FPC compiler).

[Aruna]

<snip>
In that case write a /usr/local/bin/lazarus program that handles the options properly.

Code: Text  [Select][+][-]

1. #!/bin/sh
2.  
3. # set -x
4.  
5. PROGRAM=lazarus
6. VERSION=`basename $0`
7. BINARY="/usr/local/share.lazarus/$VERSION/$PROGRAM"
8. CONFIG="$HOME/.$VERSION"
9.  
10. if [ x$1x = x+qt5x ]; then
11.   BINARY=$BINARY-qt5
12.   shift
13. fi
14.  
15. if [ x$1x = x+gtk2x ]; then
16.   BINARY=$BINARY-gtk2
17.   shift
18. fi
19.  
20. if [ ! -x "$BINARY" ]; then
21.   echo "File $BINARY does not exist or is not executable"
22.   exit 1
23. fi
24.  
25. if [ ! -d "$CONFIG" ]; then
26.   echo "WARNING: configuration directory $CONFIG does not exist"
27. fi
28.  
29. echo $BINARY --pcp=$CONFIG $@
30. exec $BINARY --pcp=$CONFIG $@
31.  

Wow, this is perfect. Thank you. It has been a while since I wrote any shell scripts :-)

Code: Text  [Select][+][-]

1. 0 1>markMLl@kdg-dev-01:/usr/local/bin$ ls -l lazarus*
2. lrwxrwxrwx 1 root root   32 Feb 20  2024 lazarus -> /usr/local/share.lazarus/lazarus
3. lrwxrwxrwx 1 root staff   7 May 15  2017 lazarus-1.0.14+2.6.4 -> lazarus
4. lrwxrwxrwx 1 root root    7 Mar  4  2017 lazarus-1.6.4+3.0.2 -> lazarus
5. lrwxrwxrwx 1 root staff   7 Jul  3  2018 lazarus-1.8.0+3.0.4 -> lazarus
6. lrwxrwxrwx 1 root staff   7 Jul  3  2018 lazarus-1.8.2+3.0.4 -> lazarus
7. lrwxrwxrwx 1 root staff   7 Jul  3  2018 lazarus-1.8.4+3.0.4 -> lazarus
8. lrwxrwxrwx 1 root root    7 Sep  8  2021 lazarus-2.0.10-2+3.2.0 -> lazarus
9. lrwxrwxrwx 1 root root    7 Nov 21  2020 lazarus-2.0.10+3.2.0 -> lazarus
10. lrwxrwxrwx 1 root root    7 Sep  8  2021 lazarus-2.0.12+3.2.0 -> lazarus
11. lrwxrwxrwx 1 root root    7 Mar 18  2020 lazarus-2.0.6+3.0.4 -> lazarus
12. lrwxrwxrwx 1 root root    7 Nov 19  2020 lazarus-2.0.8+3.0.4 -> lazarus
13. lrwxrwxrwx 1 root root    7 Jan  9  2023 lazarus-2.2.4+3.2.2 -> lazarus
14. lrwxrwxrwx 1 root root    7 Sep  2  2023 lazarus-2.2.6+3.2.2 -> lazarus
15.  

MarkMLl

Holy smokes you have 12 different versions? And way back from 2017 too.. ( I thought I was the only person crazy enough to run multiple kernels, that was till now ) Here have a look at my madness.

Code: Text  [Select][+][-]

1. aruna@debian:/media/aruna/460c8aa0-2f69-43ef-887c-0b14e6ecff68/boot$ ls -1alh  vm*
2. -rw-r--r-- 1 root root 3.0M Dec 14  2017 vmlinuz-3.16.0-4-amd64
3. -rw-r--r-- 1 root root 3.0M Jun 28  2021 vmlinuz-3.18.2
4. -rw-r--r-- 1 root root 5.5M Jun 25  2021 vmlinuz-3.18.2-testing
5. -rw-r--r-- 1 root root 5.5M Jun 24  2021 vmlinuz-3.18.2-testing.old
6. -rw-r--r-- 1 root root 4.8M Jul 20  2021 vmlinuz-5.14.0-rc2-next-20210720
7. -rw-r--r-- 1 root root 8.7M Jun 28  2021 vmlinuz-5.9.6
8. -rw-r--r-- 1 root root 4.5M Jun 26  2021 vmlinuz-5.9.6-custom
9. -rw-r--r-- 1 root root 4.6M Jun 26  2021 vmlinuz-5.9.6-custom.old
10. -rw-r--r-- 1 root root 8.7M Jun 28  2021 vmlinuz-5.9.6.old
11. -rw-r--r-- 1 root root 6.6M Jul 20  2021 vmlinuz-5.9.6-testing
12. -rw-r--r-- 1 root root 8.7M Jul 20  2021 vmlinuz-5.9.6-testing.old
13.  

That is one HD and below is another ..

Code: Text  [Select][+][-]

1. aruna@debian:/media/aruna/460c8aa0-2f69-43ef-887c-0b14e6ecff68$ ls -1alh /boot/vm*
2. -rw-r--r-- 1 root root 6.6M Mar  7  2022 /boot/vmlinuz-5.10.0-12-amd64
3. -rw-r--r-- 1 root root 6.6M Mar 17  2022 /boot/vmlinuz-5.10.0-13-amd64
4. -rw-r--r-- 1 root root 6.6M Apr 29  2022 /boot/vmlinuz-5.10.0-14-amd64
5. -rw-r--r-- 1 root root 6.6M Jun  9  2022 /boot/vmlinuz-5.10.0-15-amd64
6. -rw-r--r-- 1 root root 6.6M Jul 23  2022 /boot/vmlinuz-5.10.0-16-amd64
7. -rw-r--r-- 1 root root 6.7M Aug 13  2022 /boot/vmlinuz-5.10.0-17-amd64
8. -rw-r--r-- 1 root root 6.7M Sep  2  2022 /boot/vmlinuz-5.10.0-18-amd64
9. -rw-r--r-- 1 root root 6.7M Oct 21  2022 /boot/vmlinuz-5.10.0-19-amd64
10. -rw-r--r-- 1 root root 6.7M Dec 13  2022 /boot/vmlinuz-5.10.0-20-amd64
11. -rw-r--r-- 1 root root 6.7M Jan 21  2023 /boot/vmlinuz-5.10.0-21-amd64
12. -rw-r--r-- 1 root root 6.8M Apr 22  2023 /boot/vmlinuz-5.10.0-22-amd64
13. -rw-r--r-- 1 root root 6.8M Jul 27  2023 /boot/vmlinuz-5.10.0-23-amd64
14. -rw-r--r-- 1 root root 6.8M Aug  8  2023 /boot/vmlinuz-5.10.0-24-amd64
15. -rw-r--r-- 1 root root 6.8M Aug 16  2023 /boot/vmlinuz-5.10.0-25-amd64
16. -rw-r--r-- 1 root root 6.8M Sep 29  2023 /boot/vmlinuz-5.10.0-26-amd64
17. -rw-r--r-- 1 root root 6.8M Dec 31  2023 /boot/vmlinuz-5.10.0-27-amd64
18. -rw-r--r-- 1 root root 6.8M Jan 31  2024 /boot/vmlinuz-5.10.0-28-amd64
19. -rw-r--r-- 1 root root 6.8M May  3 08:40 /boot/vmlinuz-5.10.0-29-amd64
20. -rw-r--r-- 1 root root 6.8M Jun  1 05:24 /boot/vmlinuz-5.10.0-30-amd64
21. -rw-r--r-- 1 root root 6.8M Jul 14 04:11 /boot/vmlinuz-5.10.0-31-amd64
22. -rw-r--r-- 1 root root 5.0M Feb 24  2022 /boot/vmlinuz-5.16.10
23. -rw-r--r-- 1 root root 4.5M Mar  9  2022 /boot/vmlinuz-5.16.11
24. -rw-r--r-- 1 root root 5.0M Mar  9  2022 /boot/vmlinuz-5.16.11.old
25. -rw-r--r-- 1 root root 5.5M Mar  9  2022 /boot/vmlinuz-5.16.12
26. -rw-r--r-- 1 root root 5.5M Mar  7  2022 /boot/vmlinuz-5.16.12.old
27. -rw-r--r-- 1 root root 4.9M Mar 11  2022 /boot/vmlinuz-5.16.13
28. -rw-r--r-- 1 root root 4.9M Mar 10  2022 /boot/vmlinuz-5.16.13.old
29. -rw-r--r-- 1 root root 4.9M Mar 22  2022 /boot/vmlinuz-5.16.16
30. -rw-r--r-- 1 root root 4.9M May 16  2022 /boot/vmlinuz-5.16.16ch341
31. -rw-r--r-- 1 root root 4.9M May 16  2022 /boot/vmlinuz-5.16.16ch341.old
32. -rw-r--r-- 1 root root 4.9M Mar 19  2022 /boot/vmlinuz-5.16.16.old
33. -rw-r--r-- 1 root root 6.3M Aug 26 03:02 /boot/vmlinuz-6.10.6
34. -rw-r--r-- 1 root root 6.3M Aug 26 01:40 /boot/vmlinuz-6.10.6-lazarus
35. -rw-r--r-- 1 root root 6.3M Aug 26 02:56 /boot/vmlinuz-6.10.6.old
36. -rw-r--r-- 1 root root 6.0M Aug  3  2023 /boot/vmlinuz-6.4.8ch341
37. -rw-r--r-- 1 root root 6.0M Sep 20  2023 /boot/vmlinuz-6.4.8-CODEPAGE_437
38. -rw-r--r-- 1 root root 6.1M Feb  9  2024 /boot/vmlinuz-6.4.8-fix
39. -rw-r--r-- 1 root root 6.0M Oct 29  2023 /boot/vmlinuz-6.4.8-fix.old
40. -rw-r--r-- 1 root root 6.0M Oct 25  2023 /boot/vmlinuz-6.4.8-loop
41. -rw-r--r-- 1 root root 6.0M Aug  3  2023 /boot/vmlinuz-6.4.8-stable
42. -rw-r--r-- 1 root root 6.1M Feb  9  2024 /boot/vmlinuz-6.4.8-usb

There are some more hiding in other disks lying around :-)

@MarkMLI I have a question? I have never seen a prompt such as yours '0 1>markMLl@kdg-dev-01:/usr/local/bin$ '. I am curious to know what the 0 1 > redirection is for please?