[opensuse-packaging] Re: [opensuse-buildservice] OBS 101: How to threat packages with multiple spec files
On 01/15/2013 10:41 AM, Dominique Leuenberger a.k.a. Dimstar wrote:
Quoting Sascha Peilicke <saschpe@suse.de>:
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 <which_spec_file_to_build.spec>
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)
Hello, On Jan 15 11:11 Sascha Peilicke wrote (excerpt):
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".
Because the issue becomes more and more complicated, it seems the root cause should be solved instead of trying to make an oversophosticated workaround via link packages. I would prefer if the openSUSE build service software "just works" with source packages that contain multiple spec files. Preferably even spec files with arbitrary names that create binary packages with arbitrary names. Non matching arbitrary names are of course not a good idea in general (cause any kind of confusion) but the openSUSE build service software should not have issues with it. Otherwise every new contributor who creates a source package with multiple spec files gets all those issues again and again. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am Dienstag, 15. Januar 2013, 11:59:10 schrieb Johannes Meixner:
Hello,
On Jan 15 11:11 Sascha Peilicke wrote (excerpt):
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".
Because the issue becomes more and more complicated, it seems the root cause should be solved instead of trying to make an oversophosticated workaround via link packages.
I would prefer if the openSUSE build service software "just works" with source packages that contain multiple spec files.
Preferably even spec files with arbitrary names that create binary packages with arbitrary names. Non matching arbitrary names are of course not a good idea in general (cause any kind of confusion) but the openSUSE build service software should not have issues with it.
Otherwise every new contributor who creates a source package with multiple spec files gets all those issues again and again.
This is planned as an option for the future. However, we will not be enable it for current distros, because it changes the result of their sources. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (3)
-
Adrian Schröter -
Johannes Meixner -
Sascha Peilicke