You are not logged in.
Trying to get a deeper understanding of installation process. During installation the system is usually installed with pacstrap /mnt base base-devel. Looking at the repositories, the base & base-devel groups list all of the packages for each of these groups but where are these groups defined? pacman -Qi attr doesn't list it as a member of the base group even though it obviously is.
Error...my bad. The attr package isn't part of the base group
and performing a pacman -Qi bash does list it in the base group.
So just to confirm this. Does pacstrap query the entire package repo and pull all packages that have "base" as a group membership when you do pacstrap /mnt base?
Last edited by gillecaluim (2015-07-16 16:02:58)
Offline
The groups aren't defined in a central location. The groups are part of the package description, they are similar to tags.
attr is not a part of the base group, but a dependency of a member of this group. If you want all installed members and the dependencies, then I suggest a command like this:
pacman -Qqg base | xargs -n1 pactree -l | sort -uLast edited by progandy (2015-07-16 15:58:30)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
pacman -Qi attr doesn't list it as a member of the base group even though it obviously is.
No, it's not. It's a dependency of other packages that are in base, such as coreutils and tar.
These groups are defined by a line like
groups=('base')in the PKGBUILDs of all the group members. When you build the package, this becomes
group = basein the .PKGINFO file included in the package (one line per group).
Offline
~ % pacman -Qi attr
Name : attr
....
Groups : None
....
Required By : acl coreutils lib32-attr libarchive libcap patch tar
...
Install Reason : Installed as a dependency for another package
....I think it pretty much explains how it was installed along with base group.
Last edited by Xabre (2015-07-16 16:01:26)
Offline