Update of /cvsroot/fink/dists/10.2/unstable/crypto/finkinfo In directory sc8-pr-cvs1:/tmp/cvs-serv6689
Added Files: python23-2.3-2.info python23-2.3-2.patch Log Message: New upstream (alpha) version.
--- NEW FILE: python23-2.3-2.info --- Package: python23 Version: 2.3
Ho Hum, I have to wonder if it is a good idea to market python 2.3 Alpha 2 this way. People (like me) will see it and think "gee, a new python version" w/o realizing that it's an alpha version. Besides the question whether we should package alpha versions at all (I realize that some people release software that depedns on alpha version, but I don't have to like that nor these people <sigh>), not marking this as an alpha can on the long run cause more harm than it helps now to have access to this version.
Esp. once the real 2.3 is released (due June, see also http://www.python.org/peps/pep-0283.html). Yes with the dpkg version scheme, 2.3a comes after 2.3. However, now that we have epochs, this isn't really a problem anymore... you can release 2.3a2, 2.3a3, ..., 2.3b, 2.3rc1, etc.. And once they release 2.3, you can simply put it into epoch 1, i.e. add an "Epoch: 1" field and a BuildDepends: fink (>= 0.12.0-1).
Which reminds me, we *have* to document the epoch support!
Bye,
Max
------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
