You are not logged in.
Pages: 1
Hello :)
I'd like to obtain a list of all dependencies of a specific package, that ...
... (1) are required to compile and install the package (e.g. gcc>=5.3.0-3, libX>=0.0.1-1, ...)
... (2) are required to run executables contained in the package (e.g. libY>=0.0.1-1, ...)
... (3) can optionally be used by the executables contained in the package (e.g. libZ>=0.0.1-1, ...)
I tried to obtain these lists with pacman, expac, pactree, but I'm unable to execatly get what I want ...
Preferably, I'd like to obtain these lists without the need to have the package installed.
Thank you in advance for your answers :)
Last edited by Auch999 (2016-02-28 14:18:02)
Offline
A PKGBUILD contains variables for each of those. Get the PKGBUILD from the ABS.
The second two can be seen easily with pacman. If it isn't obvious how to do so, you should probably check the man page.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
A PKGBUILD contains variables for each of those. Get the PKGBUILD from the ABS.
Or from the packages link if you want a www interface for whatever reason.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
pacman -Si xxx
for package in official repos, they are pre-built, so no build dependencies, for aur package replace pacman with yaourt
Arch is home!
https://github.com/Docbroke
Offline
Well thanks but when I look at the PKGBUILD for 'linux' for example, there is no gcc or make mentioned as a prerequisite to build the kernel - where do these come from?
Offline
Please make an effort to search for your own answers:
https://wiki.archlinux.org/index.php/PKGBUILD
Also, this sounds very much like an XY problem - what are you actually trying to do?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Okay, I searched the wiki and it says packages are built with makepkg and the packages of the base-devel group are assumed to be installed already - so basically all base-devel packages are unmentioned build-dependencies for all other packages?
what are you actually trying to do?
I want to build an arch package in a container which only contains its build dependencies and the build dependencies' runtime dependencies.
Offline
I want to build an arch package in a container which only contains its build dependencies and the build dependencies' runtime dependencies.
This is precisely why I wrote clean-chroot-manager.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Auch999 wrote:I want to build an arch package in a container which only contains its build dependencies and the build dependencies' runtime dependencies.
This is precisely why I wrote clean-chroot-manager.
Interesting, I'll have a look
Offline
So as a follow-up-question,
since the makedepends variable of a PKGBUILD of a package does not contain the packages from the base-devel group it really needs, there is no clean way to determine the specific build dependencies (without unneeded packages from base-devel) of an arch package?
Offline
Nope.
In addition to clean-chroot-manager, you can also look at the scripts in the devtools package that will create a chroot and build in it. This is how packages in the repos are generally built.
Last edited by Scimmia (2016-02-28 15:25:42)
Online
So as a follow-up-question,
since the makedepends variable of a PKGBUILD of a package does not contain the packages from the base-devel group it really needs, there is no clean way to determine the specific build dependencies (without unneeded packages from base-devel) of an arch package?
It's assumed that you will have the base-devel package installed to do any kind of package building in ArchLinux. Just like how you need the build-essentials package in Ubuntu for the same thing, even though nobody lists it as a dependency.
Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository
Offline
Pages: 1