On Mon, Apr 04, 2011 at 11:01:59AM +0200, Michael Schroeder wrote:
On Sat, Apr 02, 2011 at 01:18:55AM +0200, Cristian Morales Vega wrote:
To make it clear. You can avoid using patches and still get the updates from the updates repository, patches only give the extra pretty information.
Uh, that's not really true. Patches not only give you some pretty information, but they also force updates. 'zypper up' will not bother the user with problems, it'll just not do the update. 'zypper patch' will force the installation of all patches, thus the user has to resolve all problems.
And for people that uses zypper to update its systems it's a lot more normal to run "zypper up" (equivalent of zypper up -t packages) than zypper up -t patch.
Maybe more normal, but your system is not secure.
Regarding the initial problem, Tumbleweed and 11.4 seem to be unrelated in the build service right now, thus there's no release number synchronization.
They are not "unrelated" at all, Tumbleweed is built on top of 11.4.
If Tumbleweed is designed to be "on top" of some other project, it should use source links for the packages.
It does. But it only includes "newer" versions of packages than 11.4 so far, so the version number will always be bigger.
That way, the build service knows that the package from Tumbleweed should get a higher release number that the one in 11.4.
*BUT*: This only makes sense if all security updates are ported to Tumbleweed right away! Otherwise you'll just get an insecure system.
That's why I didn't duplicate all of 11.4 to go into Tumbleweed to have it be a stand-alone release. But, for some library work, we will need to rebuild packages that are identical to the 11.4 version, and I will use links, but how do you create a "source link" that will keep the version number greater, than the 11.4 one? Help with this would be appreciated. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org