(again with the lack of 'reply' to all, ignore previous email please)
23. feb. 2012 19.41 skrev Christian Schneemann <schneemann(a)b1-systems.de>de>:
The parameter "target_arch" was a first try
to define which packages
has to be installed in which sysroot, but was a lot to configure in
the scheduler and the job info. So at the moment this parameter is
removed again and just "neededbyhost" is used to determine packages
for hte hostsystem.
Now all packages withouth "neededbyhost" attribute are installed in
all sysroots for additional architectures.
Don't know if this is the best way, but at the moment the easiest to
test the crossbuilding.
What do you think would be a good way for this? Should the
bdep-packages become tagged with the architecture they are needed in?
you're really planning on N sysroots, it'd be good to tag them
specifically with what sysroot to put them into, even the / one, IMHO.
Keep in mind that you might have to maintain this behaviour for a
longer time as patches will go into 'build' and 'osc' and hence be
difficult to revert on developer machines / remain compatible with
older OBS instances, so it's best to do it right the first time.
For initial development/proof of concept it makes sense to restrict to
2 roots (host and target)
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org