Re: disttags, useful?? (was Re: python 2.3 for RH7.3)

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---858510860-75408844-1103493235=:921
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by horsea.3ti.be id
	iBJLrtlr006779

On Mon, 20 Dec 2004, Jeff Pitman wrote:

> On Monday 20 December 2004 00:50, Jeff Pitman wrote:
> > Anyway, there might be other issues, but I feel these provide a
> > compelling look at a possible rethink on disttags. =A0
>=20
> Oh, and disttags causes us to go crazy about things like: where do we=20
> fit el3 or el2 in the line from rh9 -> fc3? Trying to order different=20
> lines of distros in some linear sequence doesn't work.

For different distros it does not work. But as someone once said:

	Rawhide	-> unstable
	Fedora	-> testing
	Red Hat	-> stable

If you consider this and you know el4 is extracted from fc3, it may make=20
sense to allow people to upgrade from fc3 to el4. Just like I know in=20
production rh7 is upgraded to el3 with little problems.

It may not be supported but it works and you can even do it remotely=20
without any problems. (I've done it several times with no problems)


> So, I'm just advocating Smart to be able to do a "dist-change", instead=
=20
> of upgrade and take what your current system has to any other distro. =20
> This would make possible crazy things like el2 -> chaos -> el3 -> fc3=20
> possible. Having such a mechanism would deprecate the entire idea of=20
> having disttags, making our Release munges a lot more manageable.

Smart may be a solution, but disttags don't really harm. I'm not sure why=
=20
people think disttags or repotags are harmful and should be removed from=20
Release tags.

--   dag wieers,  [email protected],  http://dag.wieers.com/   --
[all I want is a warm bed and a kind word and unlimited power]
---858510860-75408844-1103493235=:921
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
repo-coord mailing list
[email protected]
http://lists.atrpms.net/mailman/listinfo/repo-coord

---858510860-75408844-1103493235=:921--