prefix in PKGBUILDs

schnusch · 2015-02-28 11:15:31

I would recommend to make PKGBUILDs more flexible by adding the possibilty to install to a custom prefix. This would need another variable like $srcdir or $pkgdir in makepkg (say $prefix), but still provide backwards compatibility for older versions without support for this variable.

Here a patch for coreutils:

diff -urN coreutils/PKGBUILD coreutils_prefixed/PKGBUILD
--- coreutils/PKGBUILD	2015-02-28 11:40:26.205559513 +0100
+++ coreutils_prefixed/PKGBUILD	2015-02-28 11:41:44.479080115 +0100
@@ -26,8 +26,8 @@
 build() {
   cd $pkgname-$pkgver
   ./configure \
-      --prefix=/usr \
-      --libexecdir=/usr/lib \
+      --prefix="${prefix:-/usr}" \
+      --libexecdir="${prefix:-/usr}/lib" \
       --with-openssl \
       --enable-no-install-program=groups,hostname,kill,uptime
   make

I don't claim this solution to be the ideal, but I would see great use in this feature.

graysky · 2015-02-28 11:26:25

You probably want to open a feature request against pacman in the bug tracker...

Allan · 2015-02-28 16:13:58

No you don't... this is nothing to do with pacman. And I doubt Arch would support that either.

Trilby · 2015-02-28 16:16:57

Nothing needs to be added for this. Any package that supports prefix specification in the build/install will already work this way. Just define the PREFIX variable you want to use. Note that the patch in your initial post only patches a PKGBUILD. If /usr/ is hardcoded in the PKGBUILD and you'd rather have it use the PREFIX variable, report that to the maintainer of the PKGBUILD or edit it yourself.

progandy · 2015-02-28 17:23:04

I don't see a reason for a global option in makepkg for compiling a few select packages with a different prefix. Simply edit each PKGBUILD you need, that should not be too much work. Regardless, if you want to install multiple versions of a package in different locations (e.g. opt), you'll have to modify the package name and other metadata, too.

graysky · 2015-02-28 19:14:26

Allan wrote:

No you don't... this is nothing to do with pacman. And I doubt Arch would support that either.

But...

% pacman -Qo makepkg
/usr/bin/makepkg is owned by pacman 4.2.1-1

So if he wanted the dev group to see the request, why not open the FS against core/pacman?

Trilby · 2015-02-28 19:20:41

Trilby wrote:

Nothing needs to be added for this.

What feature is being requested? Variables can already be defined by users and used in PKGBUILDs.

Allan · 2015-03-01 04:01:24

graysky wrote:

Allan wrote:
No you don't... this is nothing to do with pacman. And I doubt Arch would support that either.
But...
% pacman -Qo makepkg
/usr/bin/makepkg is owned by pacman 4.2.1-1
So if he wanted the dev group to see the request, why not open the FS against core/pacman?

Filing it against pacman ensures only I see it, and not the whole dev group

graysky · 2015-03-01 04:32:16

Allan wrote:

Filing it against pacman ensures only I see it, and not the whole dev group

But you already saw it

Arch Linux

#1 2015-02-28 11:15:31

prefix in PKGBUILDs

#2 2015-02-28 11:26:25

Re: prefix in PKGBUILDs

#3 2015-02-28 16:13:58

Re: prefix in PKGBUILDs

#4 2015-02-28 16:16:57

Re: prefix in PKGBUILDs

#5 2015-02-28 17:23:04

Re: prefix in PKGBUILDs

#6 2015-02-28 19:14:26

Re: prefix in PKGBUILDs

#7 2015-02-28 19:20:41

Re: prefix in PKGBUILDs

#8 2015-03-01 04:01:24

Re: prefix in PKGBUILDs

#9 2015-03-01 04:32:16

Re: prefix in PKGBUILDs

Board footer