Mailinglist Archive: opensuse-factory (1134 mails)

< Previous Next >
Re: [opensuse-factory] Build system solutions (was Re: Calling for a new openSUSE development model)
  • From: Cristian Morales Vega <reddwarf@xxxxxxxxxxxx>
  • Date: Mon, 18 Jun 2012 19:08:44 +0100
  • Message-id: <>
On 18 June 2012 16:21, Greg KH <gregkh@xxxxxxxxx> wrote:
On Mon, Jun 18, 2012 at 11:36:49AM +0200, Vincent Untz wrote:
Le samedi 16 juin 2012, à 01:59 +0200, Jan Engelhardt a écrit :

On Saturday 2012-06-16 01:46, Greg KH wrote:

Yes, but that has not much to do wth the issue here, USE flags are not
something that openSUSE wants to get into, and it's one thing that I
think is a big problem in Gentoo, as well as a strength.

Note, I've been a Gentoo developer longer than I've been a openSUSE
developer, so I know how Gentoo works pretty well :)

Anyone know how Debian handles library checkins into their build system?
Do they always rebuild everything?  Or is there some other process to
determine if rebuilds happen?

It looks as if Debian does not have any automatic rebuilds at all.

Yes, it's a manual process. See for instance.

Ah, many thanks for that.

So, either we come up with a manual way to do this for openSUSE, or we
drown in rebuilds for no good reason (one specific example that just hit
Tumbleweed this weekend, update e2fsprogs and watch your whole distro
rebuild, that really shouldn't happen...)

An "osc whatdependson" in the form of a tree would help to know why
e2fsprogs triggers so many package rebuilds (apparently 2041 of the
It could also be handy to be able to list all the packages from
Factory sorted by the result of "osc whatdependson openSUSE:Factory
<that_package> standard i586 | wc -l" (trying to do it with a loop
could take quite a long time, and I'm not sure the OBS would like it).

Without a general solution, at least one that lets people fix problems
one by one.
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
This Thread
Follow Ups