[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Quetion about legacy support for FC1

On Fri, 2004-05-14 at 04:37, Axel Thimm wrote:

> > I think, unless people have not modified their yum.conf at all, it won't
> > work.
> >=20
> > yum.conf is marked config(noreplace) last time I checked.
> >=20
> > so a new yum will just create a yum.rpmnew
> Seth is right, almost noone leaves these config files unmodified :)
> But how about paving the path at the very birth of a release by having
> the fedoralegacy entries added at the very beginning of the life cycle
> of FC<N> pointing to an empty folder?  People will add repos and so on,
> and the legacy pointer will wait for fedoralegacy to populate the
> matching folder at EOL time, e.g.
> # The following repo will be populated when Fedora Core 2 reaches EOL,
> # which will be approximately in <compute EOL date>
> # see fedoralegacy.org for details.
> [legacyupdates]
> name=3DFedora Core $releasever legacy updates
> baseurl=3Dhttp://download.fedoralegacy.org/fedora/$releasever/updates/$base=
> arch=20
> (and fedoralegacy will have free monitoring/statistics of Fedora
> deployment ;)
> --=20
> Axel.Thimm at ATrpms.net

Definitely not a cure-all or sole remedy, but you could post a notice of
the existence of FC1 support, when it happens, in the footer generated
by the list server. Something like this:

fedora-legacy-list mailing list
fedora-legacy-list redhat com
Now supporting Fedora Core 1! For more information, see FAQ at:

I won't argue that not everyone even knows that they receive a list
generated footer with each post, but most of us do. ;0)

Just a suggestion to allow the list server to do a small part of the
support work.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]