Using pacman as the package manager
Hi,
I was debating on which package manager to use for my LFS build. I used Slackware's package manager successfully but I couldn't get Arch Linux's Pacman to work. I followed this guide for Pacman on LFS 8.1 (modified it for LFS version 9.0) but as it was mentioned in the guide "... many binaries and other files were owned by ben," which is where I also got stuck on. It was fixed by manually changing owner on those files mentioned but I don't want to be doing this every time I build and install a package. Any suggestions on how to fix this problem of having the incorrect owner on the libraries, binaries, etc.? I tried searching for a reason why pacman was doing this but I couldn't find a good answer (perhaps I'm only a white belt in Google-fu). |
There are quite a few projects on github where pacman has been added to LFS.
A google search gives me at least 7 projects. For example this one: https://github.com/EastAPOLO/lfs-pacman And even after you completed LFS you can try this: https://github.com/uditkarode/lfspacman In my opinion most existing package managers are too tightly intergrated for the specific distro. Slackware's pkgtools are so simple they can be used anywhere, next one in line is pkgutils from CRUX. What is your goal exactly? |
I know that there are several projects out there with pacman on LFS, but some of them are either
automated and/or using systemd. My goal is to build LFS manually with System V and having pacman as it's package manager. The closest one to the idea that I had in mind is the project that I've mentioned but there are some hiccups in the end, as stated in the link that you've provided: https://github.com/EastAPOLO/lfs-pacman I'm trying to understand why those problems occur towards the end in finishing up LFS using pacman. It seems that it shouldn't matter which package manager you use but you seem to be saying that each package manager is somehow closely tied with it's distro. I don't understand how that is the case. I mean, it's not like a package manager somehow "knows" distribution you're using, is it? Could you explain why and how they are tightly integrated? |
A few things make pacman not that ideal for LFS.
Pacman does not allow root to build packages without tricks. Pacman assumes a filesystem hierarchy as used by arch linux which differs from lfs. And if you are going to use pacman and the existing repos from archlinux, you will end up with arch linux. |
Quote:
https://www.archlinux.org/packages/core/x86_64/pacman/ https://www.archlinux.org/pacman/ https://git.archlinux.org/svntogit/p...ackages/pacman https://sources.archlinux.org/other/pacman/ |
Quote:
Quote:
As for building LFS, I should look into pkgutils from CRUX. I'm curious to see how to integrate that into LFS. Thanks for your suggestions/info! |
Quote:
|
@basica Ok, I will keep that in mind and try it again.
|
I just finished chapter 6 and I checked the ownership of all of the files. I wrote a script (which I think works) that checks this:
Code:
#!/bin/bash -e Code:
# grep "\-rw\-\-\-\-\-\-\-" file-list Alternatively, I was thinking of installing with pacman and then installing the "crude" way (e.g. ./configure && make && make install), but this seems cumbersome. I wonder if instead the way the instructions on github (or linuxfromscratch hints) in creating the user ben (I called it bob), if just creating a regular user using useradd would solve this issue. In other words, I wonder if it's because it's in the way this user is being created, unless I'm not understanding something. |
All times are GMT -5. The time now is 08:21 PM. |