[arch-general] Independent arch field in sub packages? (Was: Re: [commitpkg] Some stylistic cleanup)

Evangelos Foutras foutrelis at gmail.com
Wed Sep 23 17:04:21 EDT 2009


Aaron Griffin wrote:
> Actually, we might even be able to ignore the arch=() field for
> purposes of uploading here. We could just loop over a hardcoded list
> of architectures (let's face it, these won't be changing regularly).
> The dbscripts do something similar - there is an ARCHES=(i686 x86_64)
> array, and some (not all) for loops do:
>    for _arch in ${ARCHES[@]} any; do ... done

Maybe I'm over-thinking it and missing a simpler solution. I'm trying to 
be as explicit as possible, in order to avoid uploading any unneeded or 
wrong packages that, for whatever reason, may exist in the same 
directory where commitpkg is run. Another crucial point is that 
archrelease must not be executed (for the currently examined repo) if 
not all packages are present and uploaded.

At any rate, I think we'll have to retrieve sub package variables in the 
foreseeable future, when this gets implemented: 
http://bugs.archlinux.org/task/15955. It certainly looks tricky though, 
as the variables are overridden in package_*() functions which contain 
other commands as well.


More information about the arch-general mailing list