Need help coming up with a package management system
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.
Need help coming up with a package management system
Now, this is my problem. I've gotten to chapter 6, where the building of the real system begins, and it tells you to adopt a package management system. The best one seems to be the "fakeroot" approach, described here. But I've stumped on the details on how to use it. The text does a general description, but it doesn't point out the specific methods and steps to implement it.
So does anybody know some step-by-step tutorial for just one installation, to help me understand the procedures and advantages/disavdantages of this approach? I know that I'm supposed to do my own research, but Google hasn't been helpful so far and I don't have a clue on how to do this.
Yes, sorry, the "described here" was meant to be a link. I read it, and though it describes the general picture, I've no idea on how to implement this.
What, exactly, do you not understand? The steps for this method are described near the middle of the hint. Look for the paragraph beginning with, "The steps to installing a package with this approach are as follows."
The hint says to do "the appropiate maintenance" and "post install configuration". On what cases would this be needed?
It also says that the method is good for cases when a package would collide with something already installed. But how would I know if it does?
After you install the package in your fakeroot, you can see what files are installed. Compare this to existing files. If there are files installed in the same directory with the same name as files already installed, you can move them, rename them, whatever you need while they are in your fakeroot and before you create a tarball. Then, when you unpack the tarball into /, the existing files won't be overwritten. This would be appropriate maintenance.
Thanks for the advice. I understand the uses of post-installation configuration, but just one thing: I don't understand why the fakeroot system would make this any easier. It doesn't put a magical "Configure me" button on packages.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.