On Samstag, 8. Oktober 2016, 13:28:07 CEST wrote Andreas Färber:
Am 07.10.2016 um 00:25 schrieb Alexander Graf:
Am 06.10.2016 um 21:37 schrieb Andreas Färber
Am 06.10.2016 um 19:24 schrieb Alexander Graf:
>> Am 06.10.2016 um 18:12 schrieb Dirk
>> 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
> 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.
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.
JFYI, we are currently working on a mechanism to avoid the need of "_link"
packages when having multiple build descriptions in one container.
However, it will take some more time, but you may want to wait for it before
you spend too much effort here.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org