[ATrpms-users] Would it be possible to give a warning before you wipe out the Fedora8 atrpms

Jeffrey J. Kosowsky atrpms at kosowsky.org
Sun Nov 2 01:30:29 CET 2008


Fedor Pikus wrote at about 17:00:21 -0700 on Saturday, November 1, 2008:
 > On Sat, Nov 1, 2008 at 4:50 PM, Jeffrey J. Kosowsky <atrpms at kosowsky.org> wrote:
 > > Even better would be if you could retain them ;)
 > > but assuming you can't it would be good to have something like a 30
 > > day transition/warning if possible.
 > 
 > This is a serious issue. Fedora 9 has *huge* number of problems, large
 > and small. The half-baked KDE4 which, even with the update, is nowhere
 > ready for release. GDM is still missing some basic functionality like
 > auto-login. Synaptic cannot be used at all, and the developers are
 > pointing fingers at each other every few months in Bugzilla comments.
 > 
 > May be the Fedora 10 is better. But at least until it has enough
 > exposure and we know more about it, Fedora 8 is the last usable
 > release. The support for it should not be dropped until there is an
 > alternative, and right now (not counting the still-unknown Fedora 10)
 > the only alternative is Ubuntu/Gentoo/etc.
 > 
Additionally, as Linux and Fedora continue to mature, I find less and
less reason to upgrade every 6 months.
I know that Centos is available and has a longer upgrade cycle, but I
prefer the choice of upgrading to the latest when needed and then not
having to upgrade until I need it again. At least with this strategy,
for some of the time I have the latest and greatest. And then it is up
to me when to upgrade to the latest and greatest again.

Given that disk size doubles every 1-2 years (with corresponding drops
in price), I would hope that the cost of keeping old rpms available
wouuld be now quite near minimal (and as I mentioned before, if it
would help, I would be willing to send a small contribution to defray
a share of the cost). Then depending on the burden, you could decide
when (if ever) to update the old rpms for critical bug fixes/changes.

The problem for me with Centos (in my non-production environment) is
that then I am NEVER current and only get further out of date as time
passes.



More information about the atrpms-users mailing list