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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Wed, Sep 23, 2009 at 2:53 PM, Evangelos Foutras <foutrelis@xxxxxxxxx> wrote:
> Aaron Griffin wrote:
>>
>> On Wed, Sep 23, 2009 at 1:04 PM, Evangelos Foutras <foutrelis@xxxxxxxxx>
>> wrote:
>> I pushed all of your patches. The last one didn't apply cleanly, so I
>> had to do some tweaking. It was most likely related to me removing
>> trailing whitespace from the svn spacing commit.
>>
>> Thanks a lot!
>
> Thanks for applying the patches to devtools.
>
> I have a question. Currently, sub packages can't have a different
> architecture field than the main package. Are there plans to add this
> possibility in the future? This could come in handy with packages that have
> huge data files that are architecture independent and can be split into a
> sub package with arch=('any').
>
> I'm mainly asking because if the above gets implemented, commitpkg will need
> to be slightly modified in order to be able to locate -any sub packages (and
> I have a feeling that it was able to do this before my patches were applied
> :d ).

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


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux