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.
I'm trying to build LFS non-systemd and include pacman in it. LFS version is SVN-20140909. I'm having trouble finding any guide for including pacman that's somewhat new thus I do not know which packages are mandatory for pacman to compile properly.
For now I found that default configuration requires openssl which is not a pacman dependancy in Arch linux. Should I skip openssl? I see fakeroot as an optional dependancy, but I want to be able to use regular user (named whatever) for building as Arch recommends it.
Actually I would like to run pacman the same way I do it in Arch linux, but without the public keys as I will be the only one building and using packages. Does that mean to skip gpgme? In Arch I hace both Xfer commands commented out.
I'm currently at chapter 5 just before book mentions stripping. I will do the stripping once pacman is successfully installed.
The packages for this have been updated since, so try to use the versions if listed in the LFS, BLFS, and CLFS books if necessary. It also lists how to draft your own PKGBUILD scripts too.
I advise you to carefully consider the usage auto dependency resolution as some packages require dependency loops between packages. I'm not sure how pacman handles optional dependencies. I know some package managers that build from source use an ncurses interface to select optional packages per build.
Things like cairo can have circular rebuilds against other packages, so you may want to use terms like cairo-base, cairo-rebuild, etc. in each sequence.
Also, lastly, before you commit to pacman. Make extremely sure you draft everything pacman needs as far as PKGBUILD scripts go before you start building. The BLFS book will be no different. You'll have to carefully check each package as you go for instructions to craft a full set of scripts.
You can take a look at my scripts for building lfs with pacman: http://www.linuxquestions.org/questi...3/#post5020420
It was a year ago, and for lfs-7.4, but I think you can still learn from them. (Read the thread about a few things I forgot in the tarball.)
I couldn't get fakeroot to work when I compiled it for lfs-7.5. When I build packages with it, my user bacame the owner of the files. Finally I gave up, and tried the package I'd compiled in 7.4 and it worked, so I'm using that one. I haven't built 7.6-rc1 yet.
Thanks for the heads up. Pacman has no ncurses menu for such a thing but whn it encounters a dependancy loop it picks one dependancy and installs it before others, thus breaking the loop.
@Lennie
I will take a look when I find more time, thanks anyway.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.