Mailinglist Archive: opensuse-factory (837 mails)

< Previous Next >
Re: [opensuse-factory] Build Target Tumbleweed
On Thu, Mar 24, 2011 at 05:15:04PM +0100, Adrian Schröter wrote:
Am Donnerstag, 24. März 2011, 09:03:19 schrieb Greg KH:
On Thu, Mar 24, 2011 at 04:49:07PM +0100, Richard Guenther wrote:
On Thu, 24 Mar 2011, Greg KH wrote:
Tumbleweed is "just" openSUSE:11.4 with updated packages that are in
Factory pulled into it to make it easier for users to stay up-to-date
with newer stable packages.

For example, the kernel in Tumbleweed right now is at 2.6.38, while it
will remain at 2.6.37 in the openSUSE:11.4 repo for forever.

It also has updated versions of Samba and a number of other packages.
See the openSUSE wiki page for more details about what Tumbleweed is if
you are curious.

So you never update libraries in Tumbleweed? Or if you update a
library in Tumbleweed you make sure to also re-build all users
of that library in Tumbleweed?

If I update a library in Tumbleweed, I will rebuild all users of that
library in the openSUSE:11.4 tree and add it to the Tumbleweed repo so
that there are no problems.

You may want to do this via a project link plus the linkedbuild="localdep"
scheduler switch to let OBS pick the dependening packages from openSUSE:11.4
project automatically:

That's great, but that means I need to import the links to those
packages into Tumbleweed first, right? And if I do that, I thought that
obs would rebuild them as needed if the library changed. In other
words, I thought this was they way it "always" happened and that I
didn't need to set anything special like "localdep".

Or am I mistaken?


greg k-h
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups