On 01/15/2013 10:41 AM, Dominique Leuenberger a.k.a. Dimstar wrote:

Quoting Sascha Peilicke :

...

...

Am Donnerstag, 10. Januar 2013, 10:22:52 schrieb Sascha Peilicke:

...

$ osc linkpac devel:languages:python python-nose \ devel:languages:python python-nose-doc $ osc linkpac devel:languages:python python-nose \ devel:languages:python python3-nose $ osc linkpac devel:languages:python python-nose \ devel:languages:python python3-nose-doc

If only osc co would deal with those packages correctly (e.g. by using a symlink) and not checking out the same package 4 times. This is especially true for things like kernels... You can still do "osc co -u" to checkout the unexpanded sources (i.e. just the _link file). However, due to the generic (and hugely overused) nature of the link feature, it's not always easy to find out

On 01/15/2013 01:54 AM, Hans-Peter Jansen wrote: programmatically what the packager is about to do with a package containing links.

Actually, in above example (with multiple spec files in one package) I usually ONLY care for the 'main' one (where all others link to). That one being checked out and not the _link'ed ones is sufficient... all modifications have to happen in this package anyway (not the linked ones).

And to do local builds, I just do osc build

so, not checking out the kernel 10 times for each branch would be a big bandwidth and time saver :)

Sure, I totally agree. So the magic that would have to go into "osc up" is "If _link points to same project than and the OBS package that is currently looked at corresponds to a spec file in the _link'ed OBS package, do an unexpanded checkout else do expanded". Doesn't sound too hard, no? -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)