Automating makepkg and pacman -U

huzo11 · 2018-11-13 12:06:18

Hello all.

So I was trying to write a simple python script to automate installing dependencies of AUR packages. However, I got confused when I got into the step of downloading the package files and installing them. The part involving creating package files is straightforward. But there is a slight problem when I want to automate the "sudo pacman -U packagename" part. I do not know the full name of the file that was formed by makepkg. What would be an easy way to get the package file's exact name?

Thanks.

Allan · 2018-11-13 12:12:07

Try "makepkg --packagelist". Or just do a "makepkg -i" to install them after build.

huzo11 · 2018-11-13 12:13:27

Allan wrote:

Try "makepkg --packagelist". Or just do a "makepkg -i" to install them after build.

This is great! Thanks.

Trilby · 2018-11-13 14:24:38

Remember the --asdeps flag if you use `makepkg -i` (well, remember it with pacman -U too, but it's easier to forget with makepkg).

huzo11 · 2018-11-13 14:55:18

Trilby wrote:

Remember the --asdeps flag if you use `makepkg -i` (well, remember it with pacman -U too, but it's easier to forget with makepkg).

According to the official website:

--asdeps <package>
Mark a package as non-explicitly installed; in other words, set their install reason to be installed as a dependency.

That is interesting. What would be different if you do not install it as a dependency? As a guess, would it only act as a dependency and not be accessible directly by the user?

eschwartz · 2018-11-13 15:11:13

It would mean when removing a package with -Rns, you would not remove the no-longer-needed dependency, because pacman thinks you explicitly want that package.

It would mean if you use pacman -Qe to list explicitly installed packages, or pacman -Qqdt to list unneeded packages which are orphaned, you wouldn't be able to distinguish between this package and packages you actually care about.

Arch Linux

#1 2018-11-13 12:06:18

Automating makepkg and pacman -U

#2 2018-11-13 12:12:07

Re: Automating makepkg and pacman -U

#3 2018-11-13 12:13:27

Re: Automating makepkg and pacman -U

#4 2018-11-13 14:24:38

Re: Automating makepkg and pacman -U

#5 2018-11-13 14:55:18

Re: Automating makepkg and pacman -U

#6 2018-11-13 15:11:13

Re: Automating makepkg and pacman -U

Board footer