Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
To my understanding, when you compile a package, it may link to other packages already installed. I'm not sure what this linking means other then the package being compiled knows this other package is there and now expects it to be there when it runs.
The main question is, say I compile packageB. PackageB sees packageA that's already installed. Now I need to recompile packageA. Do I also need to recompile pacageB because packageA has changed?
Distribution: Linux From Scratch, Slackware64, Partedmagic
Posts: 3,137
Rep:
it depends on the changes to the package you are linked against, usually a minor revision change will not cause a problem, if there is a major version change then you may have to recompile packages that are linked against the one you are updating, if you need to do this it will be in the README or CHANGELOG files, you may be lucky that the part of the library you need to use has not changed or if it has changed too much or gone away altogether the app linked sgainst the library may just segfault with no warning.
The moral of this is read the documentation and if in doubt 'suck it and see'.
The main question is, say I compile packageB. PackageB sees packageA that's already installed. Now I need to recompile packageA. Do I also need to recompile pacageB because packageA has changed?
Thanks!
In that case it is best to first upgrade A before recompiling/upgrading package B.
Is there a simple way to know what packages are linked to the package you want to replace with a newer version? I can see how this can get out of hand quickly because these other packages may be linked into other packages as well.
Distribution: Linux From Scratch, Slackware64, Partedmagic
Posts: 3,137
Rep:
Quote:
Originally Posted by GameCodingNinja
Is there a simple way to know what packages are linked to the package you want to replace with a newer version? I can see how this can get out of hand quickly because these other packages may be linked into other packages as well.
If you want simple and for the OS to do it all for you use ubuntu
Seriously one of the main drawbacks of LFS is no dependency checking, but then again the system can't update anything by itself ( unlike the aforementioned 'Linux for dummies' distro ), so if you are going to update a library etc its up to you to make sure it doesn't break anything and to update anything that you need to, with (B)LFS you are the boss!
What you could do is use a dependency tree.
Check for each package what it requires according to the book and what you installed of the recommended stuff.
A lot of work and sometimes some packages get new dependencies or new packages arise.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.