Quetion about legacy support for FC1

[Jesse Keating]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 14 May 2004 01:37, Axel Thimm wrote:
> Seth is right, almost noone leaves these config files unmodified :)

The goal isn't necessarily to have it dumped into their config 
automagically, just make it easier for them.  Having the config file 
there, even in .rpmnew is better than nothing.

> 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=Fedora Core $releasever legacy updates
> baseurl=http://download.fedoralegacy.org/fedora/$releasever/updates/$
>basearch
>
> (and fedoralegacy will have free monitoring/statistics of Fedora
> deployment ;)

That is a very interesting idea!  I will certainly think this over.

- -- 
Jesse Keating RHCE      (http://geek.j2solutions.net)
Fedora Legacy Team      (http://www.fedoralegacy.org)
GPG Public Key          
(http://geek.j2solutions.net/jkeating.j2solutions.pub)

Was I helpful?  Let others know:
 http://svcs.affero.net/rm.php?r=jkeating
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFApN1s4v2HLvE71NURAv7tAKCJ6woSS1WjkKQnrlEiDpXyXoQp+gCgg8c9
Qseb65DW/zStgOUgOfArgRc=
=kwhX
-----END PGP SIGNATURE-----