You are not logged in.
Hi all,
I am trying to save automatically the package PKGBUILD when I install a package with an aur helper. I use packer and aurget.
I modified makepkg.conf and set this relevant variables:
#########################################################################
# PACKAGE OUTPUT
#########################################################################
#
# Default: put built package and cached source in build directory
#
#-- Destination: specify a fixed directory where all packages will be placed
#PKGDEST=/home/packages
PKGDEST=/var/cache/pacman/pkg/aur
#-- Source cache: specify a fixed directory where source files will be cached
#SRCDEST=/home/sources
SRCDEST=/var/cache/pacman/pkg/aur/srcThe PKGDEST works fine and packages are saved in the specified path.
However SRCDEST variable doesn't seem to work, as I expected the PKBUILDs and other sources to be saved there, but there are no files in the path.
In the end what I am trying to emulate is something similar to ABS but for installed packages from AUR.
Last edited by adrianbs (2012-01-29 12:18:41)
Offline
That's because the source files are only cached, not saved...
I use this simple wrapper for cower:
#!/bin/sh
# install AUR packages with cower
cd $HOME/Build && cower -d "$1"
builddir="$_"
cd "$builddir" && $EDITOR PKGBUILD
makepkg -si && cd - &>/dev/null
read -p "Remove Build directory? [Y/n]? " yn
if [ "$yn" = "y" ]; then
printf "\n%s\n" "Removing build directory..."
rm -rf "$builddir"
else
printf "%s\n" "Build completed."
fiOffline
Uh, Jason... isn't that what this is for?
% cat ~/.config/cower/config | grep TargetDir
#TargetDir =
TargetDir = /var/abs/local/aurAllan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
It could be.
But having a config file for a single line could also be considered bloat ![]()
Offline
SRCDEST is where any remote files downloaded during "makepkg" are stored. SRCPKGDEST is where the tarball generated using "makepkg --source" (which contains the PKGBUILD etc) is stored.
Online
Thank you all. I'll try both solutions.
Offline
It could be.
But having a config file for a single line could also be considered bloat
And having a 10-line script isn't =p?
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
Cower (as awesome as it is) doesn't open the PKGBUILD in vim, build the package and then ask if you want to keep the build directory.
I reckon my 10 lines are pretty well spent... ![]()
Offline
Cower (as awesome as it is) doesn't open the PKGBUILD in vim, build the package and then ask if you want to keep the build directory.
I reckon my 10 lines are pretty well spent...
Cower doesn't but pacaur (which wraps it) does ![]()
It has an option it the config file to keep the build dir.
Offline
jasonwryan wrote:Cower (as awesome as it is) doesn't open the PKGBUILD in vim, build the package and then ask if you want to keep the build directory.
I reckon my 10 lines are pretty well spent...
Cower doesn't but pacaur (which wraps it) does
It has an option it the config file to keep the build dir.
And for only an extra 872 lines of code... ![]()
Offline