On Sat, May 14, 2011 at 12:48:37PM -0400, Greg Freemyer wrote:
On Sat, May 14, 2011 at 10:42 AM, Greg KH
wrote: The updates repo does not delete the packages it updates. One is always the newest that gets installed by default, but every incremental package is still there also.
I don't think you understand the amount of disk space that would take up over time...
I don't know how to address the space issue, but I think this is a significant issue.
I'm new to rolling updates, but if one of the eventual targets of Tumbleweed is servers, there needs to be way to roll a consistent set of updates to first a test server, and then to production servers.
Um, the idea of a "constantly rolling update" is in contrast to a "consistent set of updates", they are not the same thing, nor are they supposed to be. They both fit a different need.
I don't think Tumbleweed has any design goal yet to support that use case.
That is explicitly NOT the design goal of Tumbleweed at this point in time.
I don't know if the soon to be released OBS 1.3 will make doing so easier or not.
I don't know either.
For now, is it safe to say Tumbleweed doesn't address consistent rollout needs as required by production systems and therefore is not a good choice for that use? If so, I can update the wiki page.
Tumbleweed also doesn't support making me a jelly sandwich every day for lunch, should that be on the wiki as well? :) Seriously, saying all the things that Tumblweed isn't really isn't helpful, saying what it is, is. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org