On 1/24/2012 9:25 AM, Claudio Freire wrote:
On Tue, Jan 24, 2012 at 11:22 AM, Bryen M Yunashko<suserocks@bryen.com> wrote:
What I'm simply trying to say is: just because 11.3 is itself EOL, that doesn't mean OBS projects should start dropping the 11.3 repo right away.
Do others not agree?
-Archie
I'm going to assume that the EOL'ed repos get dropped due to storage conservation reasons. (only an assumption.) If that is the case, what do you propose is the length of time such repos should exist?
Not only that, it's sometime not easy to keep the packages building on old distros.
It's difficult but I do it all the way back to 10.0 for most of my stuff and the availability of say the current openssh on production boxes that can't lightly be replaced is worth a lot more than the prettiness of the spec file or the time it took for one guy to produce it. In that particular case it was pretty easy to get openssh building back to 10.2, but I have a problem I may or may not solve that prevents it on 10.1 & 10.0. But 10.2 is pretty good and worth doing. I only have a few 10.0 and 10.1 boxes and a lot more 10.3 and up. Another scenario is, maybe you can't continue to track the current version of something, but it's still very valuable to have whatever was the last version that _did_ build in that environment. It's usually far newer than whats' in the oss or updates repo, and often new enough to get you by some other otherwise impasse. For instance, maybe I can't get php5.3 built on 10.1, but maybe 5.2 did build? Well the current codeigiter can use php 5.3 or 5.2 but not 5.1.7 that came with OS 10.1. So if I have a range of boxes in production, including some 10.0 and 10.1, and I want to start working on some new projects and I want the developers to use codeigniter, it means I can actually deploy the current codeigniter everywhere. If I had been tracking openssh in my home obs project earlier than a few weeks ago, maybe I still wouldn't have the current version on 10.0, but I'd surely have a lot newer version that what my 10.0 and 10.1 boxes are stuck with now. Wherever along the way it stopped being buildable, it was long after the day the 10.0 oss repo was published or even the final update to the updates repo, and I would _love_ to have that package right now. Having a repo that builds against a given old OS version, and tracks packages as long as it can, and simply stops updating packages once they can no longer be built in that environment, but does not delete those final package versions whatever they were, is very valuable for years afterwards. -- bkw -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org