On 03/29/2018 06:03 PM, Andreas Schwab wrote:

On Mär 29 2018, Henne Vogelsang wrote:

...

Factory speaking: AFAIK Factory won't allow multibuild packages currently for some reason. Don't know if this is still correct. $ osc ls openSUSE:Factory glibc

Andreas.

ok. This means we *can* use multibuild. Thanks! -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On 04/20/2018 11:56 AM, Dominique Leuenberger / DimStar wrote:

On Thu, 2018-03-29 at 18:09 +0200, Jordi Massaguer Pla wrote:

...

On 03/29/2018 06:03 PM, Andreas Schwab wrote:

...

On Mär 29 2018, Henne Vogelsang wrote:

...

Factory speaking: AFAIK Factory won't allow multibuild packages currently for some reason. Don't know if this is still correct. $ osc ls openSUSE:Factory glibc

Andreas.

ok. This means we *can* use multibuild. Thanks! Yes, _multibuild is acceptable - but keep in mind if we are talking about ring packages, that ALL flavors must be built in the specific ring. And depending on what the dependencies are, this won't be liked much.

This is the package: https://build.opensuse.org/request/show/598539 Should we add the _multibuild ? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On Fri, 2018-04-20 at 12:48 +0200, Jordi Massaguer Pla wrote:

On 04/20/2018 11:56 AM, Dominique Leuenberger / DimStar wrote:

...

On Thu, 2018-03-29 at 18:09 +0200, Jordi Massaguer Pla wrote:

...

On 03/29/2018 06:03 PM, Andreas Schwab wrote:

...

On Mär 29 2018, Henne Vogelsang wrote:

...

Factory speaking: AFAIK Factory won't allow multibuild packages currently for some reason. Don't know if this is still correct.

$ osc ls openSUSE:Factory glibc

Andreas.

ok. This means we *can* use multibuild. Thanks!

Yes, _multibuild is acceptable - but keep in mind if we are talking about ring packages, that ALL flavors must be built in the specific ring. And depending on what the dependencies are, this won't be liked much.

What is "ring packages" ? And what is "specific ring"?

https://en.opensuse.org/openSUSE:Factory_development_model The distro is built in three rings, each more complex and building on top of the other: Ring0: bootstrap (minimal stuff so we can build more, so rpm, gcc, make) Ring1: A minimal graphical environment, and capability to build a DVD Ring2: GNOME and KDE desktops, a full DVD set, consistently able to be used for upgrades For the ring packages, we know that they should be buildable at all times, no package can be checked in that would break the build of any other ring package. Anything else is non-ring and 'just an accumulation of packages in the distribution'. In the staging process you see the difference in the way it's staged: Anything going through an adi:<X> is non-ring. In you case, nginx, is a non-ring package and there is no worry to use _multibuild. cheers Dominique

On Fri, 2018-04-20 at 13:14 +0200, Philipp Thomas wrote:

* Dominique Leuenberger / DimStar (dimstar@opensuse.org) [20180420 12:51]:

...

For the ring packages, we know that they should be buildable at all times, no package can be checked in that would break the build of any other ring package.

So if I get this right, graphviz would be a candidate for multibuild but coreutils not?

Let's start with the 'easy one': coreutils. This currently has two spec files, coreutils.spec and coreutils=testsuite.spec. Coreutils is a ring0 package (needed for bootstrap). If this were to contain a _multibuild, then coreutils-testsuite would require to be built in ring0 too, which is, due to the added build deps, not realistic. for graphviz: This consists of graphiz.spec and graphviz-addons.spec. Both are already in ring1 and needed for the minimalX building. as such, changing this into a _multibuild package would be acceptable and not cause trouble. cheers Dominique

On Apr 20 2018, Dominique Leuenberger / DimStar wrote:

Let's start with the 'easy one': coreutils. This currently has two spec files, coreutils.spec and coreutils=testsuite.spec. Coreutils is a ring0 package (needed for bootstrap). If this were to contain a _multibuild, then coreutils-testsuite would require to be built in ring0 too, which is, due to the added build deps, not realistic.

There is a special rpm condition `ringdisabled' that can be used to exclude the subpackage that should not be built in the ring project. See the glibc specfile for an example. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org