Am 07.10.2016 um 00:25 schrieb Alexander Graf:
> Am 06.10.2016 um 21:37 schrieb Andreas Färber <[email protected]>:
>> Am 06.10.2016 um 19:24 schrieb Alexander Graf:
>>>>> Am 06.10.2016 um 18:12 schrieb Dirk Müller <[email protected]>:
>>>>> and the SRs are ready. However, due to the current structure
>>>>> of _links in the ARM projects on OBS merging will probably
>>>>> break some if not most of those, as told by afaerber.
>>>>
>>>> it only breaks those that have real modifications, which should be
>>>> rare (modifications should be contributed back to the parent JeOS
>>>> package). so I don't think it is a very difficult problem.
>>>>
>>>>> Suggestions, opinions?
>>>>
>>>> I'm fine with the suggested changes, although cpp on shell is
>>>> terrible. if we could split the script into parts that are simply
>>>> appended to a common part (because usually order does not matter),
>>>> then I think that might be a  simpler solution for avoiding that
>>>> problem.
>>>>
>>>> I'm not fully convinced that it is a really frequent problem though .
>>>
>>> We made all conditionals runtime conditionals a while back to get rid of 
>>> those problems. Just push contrib changes into the main jeos package and 
>>> you're safe :)
>>
>> Please read my mail about JeOS cleanups. At least Dirk was CC'ed.
>>
>> https://lists.opensuse.org/opensuse-arm/2016-09/msg00032.html
>>
>> The problem is that we have more and more Contribs where we have _both_
>> a downstream and an upstream version for the same board. Whenever .tgz
>> files are updated in the main repo, those Contrib branches break. You
>> can't just push everything into the main JeOS package then, because at
>> least the repo needs to differ.
> 
> So can we just name them differently then? That should solve it, right? Maybe 
> by convention call downstream images ..._downstream always? That way it also 
> propagates to the image name.

Is there no way we can just avoid .tgz files altogether and use the
scripts directly? Those would be much easier to merge then and would
avoid spamming Factory:ARM with random downstream stuff.

If using a different image name, same as for your _aarch64, we'd always
get a lengthy || expression for the image name. Unless we special-case
that too and translate it to some IS_DOWNSTREAM or so.

Regards,
Andreas

P.S. Your mailer keeps screwing up the indentation of "Am ..." :/

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to