Re: PyVault Nomenclature

On Mon, May 10, 2004 at 08:18:01AM +0800, Jeff Pitman wrote:
> On Monday 10 May 2004 01:03, Axel Thimm wrote:
> > just a general question, do you want to extend to non-Red Hat
> > distributions (in the future) or will you only consider Red
> > Hat/Fedora?
> 
> Possibly. Although, I'd be hard-pressed to maintain that many.

If you make sure your python base package works on these you could
even possibly have one rpm for all. Conquer the world! ;)

> > On Mon, May 10, 2004 at 12:20:02AM +0800, Jeff Pitman wrote:
> > > For versioning, I'll try to stick with what's
> > > mainstream (ie, python2.3-2.3.3-3.pyv.0.rh90).
> >
> > I'd suggest to move the repotag (pyv) to the end of the comparison
> > string, e.g. python2.3-2.3.3-3.rh9.pyv (to make the repotag less
> > important than the disttag from an rpm upgrading POV)
> 
> Arghh!  I lied to you.  It was a late night post.  This is what it looks 
> like:
> 
> python2.3-2.3.3-7.rh73.pyv.i386.rpm

Looks nice :)

> Now if someone can give me some enlightenment about vepoch, I'd be 
> slightly interested.  But, it seems to me like a nuclear warhead 
> approach to versioning.

vepoch is used in the fedora.us naming guidelines, that contain a
major/minor split of the build number around a repotag, e.g. 0.fdr.7.
You don't need it in the above scheme.

> But, I still wonder about these:
> 
> XXX - Do we want all lowercase, or bumpy text matching original package 
> name?
> 
> XXX - Upper or lower case?

If you want to change case go with lower, as upper reminds too many of
us of FORTRAN ;)
(and shouting packages are not nice)

While there is a polica at Red Hat to use lower case it is almost
nowhere (including Red Hat) implemented. Looking at Rawhide's srpms I see

4Suite aspell-pt_BR Canna ElectricFence fonts-ISO8859-2 fonts-KOI8-R
FreeWnn GConf GConf2 Glide3 Glide3 Gtk-Perl Guppi ImageMagick libIDL
Maelstrom MagicPoint MAKEDEV MAKEDEV miniChinput MyODBC MySQL-python
Omni openCryptoki ORBit ORBit2 perl-Archive-Tar perl-Bit-Vector
perl-BSD-Resource perl-Compress-Zlib perl-Convert-ASN1
perl-Crypt-SSLeay perl-Date-Calc perl-DateManip perl-DBD-MySQL
perl-DBD-Pg perl-DBI perl-Devel-Symdump perl-Digest-HMAC
perl-Digest-SHA1 perl-File-MMagic perl-Filter perl-Filter-Simple
perl-Frontier-RPC perl-HTML-Parser perl-HTML-Tagset perl-Inline
perl-LDAP perl-Net-DNS perl-Parse-RecDescent perl-Parse-Yapp perl-PDL
perl-RPM2 perl-RPM-Specfile perl-SGMLSpm perl-TermReadKey
perl-Text-Kakasi perl-TimeDate perl-Time-HiRes perl-URI
perl-XML-Dumper perl-XML-Encoding perl-XML-Grove perl-XML-LibXML
perl-XML-LibXML-Common perl-XML-NamespaceSupport perl-XML-Parser
perl-XML-SAX perl-XML-Twig pyOpenSSL PyQt PyXML Regina SDL SDL_image
SDL_mixer SDL_net SysVinit THE ttfonts-zh_CN ttfonts-zh_TW unixODBC
VFlib2 Wnn6-SDK Xaw3d

This is slightly less than 10%, so a non-insignificant number of
packages. And most packages are from the perl domain.

I'd recommend leaving the case as used upstream.
-- 
Axel.Thimm at ATrpms.net

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

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

iD8DBQFAny6vQBVS1GOamfERAoVUAJ0f1hWFFByiX1auYHlhSJIi48OE7ACdHcyV
bBvBEcmvzldrymWoiLrVJnY=
=Conm
-----END PGP SIGNATURE-----