Linked by Thom Holwerda on Mon 30th Oct 2006 19:43 UTC, submitted by Charles A Landemaine
Thread beginning with comment 177481
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Perhaps, but it would be tricky at best, and once again just a hack. I think that the PBIs need to handle this automagicly.
My idea is to add a "global libraries" list into the PBI creator, and also versions. So eg: you fill in "libgtk-12.so" version: "x.y.z".
The PBI would make some dir like /Programs/GlobLibs/libname/libversion and map it.
Uninstallation would be like in window (lib xx is not used by any other software, do you wisht to remove it?).
This would be clean solution which should work, but I'm sure there are hidden pitfalls as well.




Member since:
2006-01-16
There are only a few cases when extra libraries needs to be included in the PBIs - and the only drawback they have is increased memory usage (due to loading libraries twice), but only if you happen to be running some of these progs in parallel. How much RAM we are talking here? 500K? 2Mb? LOL.
NO!
I'm the creator of LAZARUS PBI. See the forums for more info.
Long story short, if you need a PROGRAM which MAKES OTHER PROGRAMS and they ALL NEED THE LIB you're in a big bad problem.
You can either manualy put your required libraries to global lib directory, risking package/port corruption, or not, making your software work, but not it's products.
Eg: a compiler with IDE, see Lazarus PBI discussion in PCBSD forum. I gave up on PCBSD because of this and KDE (I prefer gnome)
So PRETTY PLEASE, stop spreading sweet ignorance