DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:from:to:content-type:date:message-id:mime-version:x-mailer
         :content-transfer-encoding;
        b=IAcj5v1dxAhdUtlTxfNm/hC7L2higK4TqLGPKHxJCQW55eFWgY10B+a9lo0qpfhUaV
         Fo+LZoal034AyPdTGOaQJjbrbDmOpH7YniiMUlC7s+++Mdu6tS3HmBRp8G3ZoW4hUez+
         lo34BeuvvXok8rn+Z/VhDQz/MVTeA2Rh76Xf8=
Subject: [alpine-devel] RFC: special variable builddir in APKBUILDs?
From: Natanael Copa <natanael.copa@gmail.com>
To: alpine-devel@lists.alpinelinux.org
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 06 Nov 2009 13:44:20 +0100
Message-ID: <1257511460.1929.594.camel@ncopa-desktop.nor.wtbts.net>
Precedence: list
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

Hi,

Just wondering if we should implement a special variable $builddir in
APKBUILDs.

This will do the same as $S in gentoo ebuilds, that is, define in what
dir the sources are supposed to be build from.

The idea is, if defined the following "magic" will happen:

* all *.patch *.diff files listed in $source will be applied with -p1
(unless prepare() function is defined in APKBUILD)

* before entering the use funcs prepare(), build(), package(), abuild
will "cd $builddir"


Benefit is that in the apkbuild, you will only need to define 

  builddir="$srcdir"/$pkgname-$pkgver

in global scope (or it coudl be predefinied as that), then can patches
automatically be applied from the default prepare() function and the
build() and package() function does not need the initial 

  cd "$srcdir"/$pkgname-$pkgver


Drawback is that now we add more "magic" functionallity and its not so
obvious whats going on when you read the APKBUILD.

What do you think?

-nc



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---