[arch-ports] PKGBUILD and package release thoughts

[eliott at cactuswax.net]

I appreciate the goal of joining multiple architectures into a single
pkgbuild, but I haven't heard much (at least that I remember) lately about
how pkgbuilds with different build requirements based on architecture are
going to be handled.

Are there going to be seperate "build" definitions, based upon architecture?
i686_build()
ppc_build()

or is there going to be some type of variable testing inside a single
build defintion...
build() {
 if [ $ARCHx = "i696x" ]; then
    <custom stuff here>
 fi
}

Also, would there be seperate file sections? If one architecture requires
a patch that another one doesn't, are all files fetched for build
regardless?

I suppose I am saying that a little more background into how the overall
structure is going to work, may help make informed opinions about
versioning conventions.

I apologize if I missed the discussion of the above, and this has already
been covered.


> On Fri, Mar 10, 2006 at 06:43:14PM -0500, Dusty Phillips wrote:
>> Would it be possible to use an array (or dict ;-)) of architecture
>> releases instead of multiple variables? This would restrict it to one
>> line in the PKGBUILD. I guess we could also have convention of
>> semi-colon separating the arch-pkg-rel variables to conserve space.
>> Really don't like how long these things are getting... :(
>>
>> Dusty
>
> Something like that would require parsing.  Bash doesn't support any sort
> of associative arrays, so we'd end up doing something like how depends
> version marking works ie.
>
> arch_rels=('i686=3' 'amd64=2')
>
> Jason
>
> --
> If you understand, things are just as they are.  If you do not understand,
> things are just as they are.
> _______________________________________________
> arch-ports mailing list
> arch-ports at archlinux.org
> http://www.archlinux.org/mailman/listinfo/arch-ports
>