Re: Practice, use, design and implementation of rpm

--===============6846299078475664164==
Content-Disposition: inline
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="lEGEL1/lMxI0MVQ2"


--lEGEL1/lMxI0MVQ2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Oct 02, 2004 at 02:06:49AM +0800, Jeff Pitman wrote:
> On Saturday 02 October 2004 00:53, Axel Thimm wrote:
> > If/When repo-coord comes to any good suggestions on rpm extensions,
> > we can summarize the outcome and present it here :)
>=20
> So, where do we go from here?  Past discussion points really have never=
=20
> been driven to a consensus.  Good arguments have been presented but=20
> we've never driven across a consistent front on the issues.  I realize=20
> some of these things may take time as more and more implementations are=
=20
> out in the wild.

The good news are that the differences were on the implementation side
of what to put into disttags, not about disttags themselves.

So while it has become rather accepted by many parties to have

   foo-1.2.3-<buildid><opt_repotag>.src.rpm
   foo-1.2.3-<buildid><disttag><opt_repotag>.<arch>.rpm

the contents of disttag have been varying. But for extending rpm to
allow the above scheme you don't need to know how the disttag will
look like on distribution XYZ.

In light of defining something larger than our rim of the teacup
(e.g. not only for the one or two distributions we are personally
focusing at) these difference become refinements, and we may have an
easier going if we keep things more abstract at the beginning
(e.g. not discussing my-favourite-scheme).

I think many of the past arguments will become more evident as we do a
top-down approach and we will finally have better grounds for
convergence.

What would be nice to achieve is to get representatives from the major
distributions. Most people on repo-coord are RH/FC only. It would also
help if before emerging new strategies the different distributions
would lay out their current schemes and workarounds.
--=20
Axel.Thimm at ATrpms.net

--lEGEL1/lMxI0MVQ2
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBXZ+LQBVS1GOamfERAn+5AKCBGoqXZsDV5kjzz+AMeMmO3IJg+ACfdmiN
U+TknXvuF6Dx7mGwV8NU0cE=
=WiQ6
-----END PGP SIGNATURE-----

--lEGEL1/lMxI0MVQ2--


--===============6846299078475664164==
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

--===============6846299078475664164==--