Arch Linux

ulixes

Member

Registered: 2010-02-09

Posts: 18

makepkg -p and install files

Hi,

i have a local, personal repository with following structure

.
├── abs 
│   ├── ...
│   └── <reponame>
│       ├── ...
│       └── <pkgname>
│           ├── PKGBUILD
│           └── ...
├── build
│   ├── ...
│   └── <reponame>
│       ├── ...
│       └── <pkgname>
│           ├── src
│           ├── pkg
│           └── ...
└── pkg
    ├── ...
    └── <reponame>
        ├── *.pkg.{xz,gz,...}
        └── <reponame>.db.tar.gz

I'm building packages by executing this single command within the build/<reponame>/<pkgname> directory:

export PKGDEST=<path-to-'pkg'>/<reponame> && makepkg -p <path-to-'abs'>/<path-to-'buildscript'>

This doesn't clutter my abs directory where the build instruction files are located, the build process itself is done in its own directory, and the output package is stored in a directory known by pacman. Everything without the need of manually copying any files as opposed to the ABS wiki page.

The Problem:
If the PKGBUILD file contains an option about an install script which is located in the same directory as the PKGBUILD, makepkg complains about missing install files. I've already tried to add the install script in the source option array, but this doesn't work too. Does the -p option only observe the buildscript?

Is there a better way to do a three step 'build instruction'-'build'-'package destination' process, without manually copying PKGBUILD and install files?

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,111

Website

Re: makepkg -p and install files

This is a limitation of makepkg. Sounds like you want the BUILDDIR environment var that we're introducing in pacman 4.0 which will let you specify a different directory to build from. However, it's not going to honor your hierarchy so easily, since you further subdivide by repository.

---

blog | ±github

ulixes

Member

Registered: 2010-02-09

Posts: 18

Re: makepkg -p and install files

Ok, i'll stick with rsyncing the 'abs' tree to the 'build' tree so far. The BUILDDIR environment variable sounds quite useful. If i undestand this variable correctly by its name, i could make a

export PKGDEST=<path-to-'pkg'>/<reponame> && export BUILDDIR=<path-to-'build'>/<reponame>/<pkgname> && makepkg

inside the 'abs' tree. To ease the command i could also make a special makepkg.conf for this repository, so i don't have to export these environment variables every time.