Mailinglist Archive: opensuse-buildservice (266 mails)

< Previous Next >
Re: [opensuse-buildservice] OBS 101: How to threat packages with multiple spec files
On 01/15/2013 01:54 AM, Hans-Peter Jansen wrote:
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
programmatically what the packager is about to do with a package
containing links.

If it's a link to a distribution (like Factory), you would want to work
on the sources or branch from it (and don't care). If you have multiple
spec files to work on you have to use the above cludge (and it's sort of
an abuse of the link feature actually). But you almost always want the
expanded sources. So I'd say the current situation is good enough, but
you could do a feature request for the OBS to thread several spec files
in one OBS package better ;-)
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)

< Previous Next >