On Sun, Feb 20, 2011 at 07:06:51PM +0200, Ionuț Bîru wrote:
> On 02/20/2011 07:04 PM, Magnus Therning wrote:
>
> >>>>The source array is modified based on files in the dir holding the
> >>>>PKGBUILD, like this:
> >>>>
> >>>>if [[ -f my.patch ]]; then
> >>>>sources=(${sources[@] my.patch)
> >>>>fi
> >>>>
> >I modified the little build script used by makechrootpkg
> >(/chrootbuild) to export SRCDEST, but that still didn't do it. How
> >can I detect within a PKGBUILD that the build is invoked by
> >makechrootpkg in an elegant way?
> >
> >/M
> >
>
> i don't understand why you want to split like that the sources
> array. Just declare it once and get over it.
>
> sources=(link1 my.patch)
>
> makepkg -g >> PKGBUILD
There are good reasons for it. I'm not talking about one PKGBUILD
here, but rather about 200, all of which are automatically generated.
Some of the 200 packages do need minor changes though, and earlier
that was done by manually modifying the output. I'm now making
some changes to the transformer so that it can pull those changes in
via patches instead. Using this type of modifications to the sources
array makes it easy to use an almost completely generic PKGBUILD.
Hopefully that explains why I'm pushing this.
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: magnus@xxxxxxxxxxxx jabber: magnus@xxxxxxxxxxxx
twitter: magthe http://therning.org/magnus
I invented the term Object-Oriented, and I can tell you I did not have
C++ in mind.
-- Alan Kay
Attachment:
pgpl0bV84lK2e.pgp
Description: PGP signature
