So, now that we have py25-* and even py30-* ports, let's do something about it. Renaming py-* t- py24-*. could be done in a simple perl regex like this
$ find dports \! -path '*.svn*' -type f -print0 | xargs -0 perl -i -pe 's/py-/py24-/g' It might be better to leave py-* ports without any changes for a while to avoid confusion. Any comments? On Feb 3, 2008 8:41 AM, Ryan Schmidt <[EMAIL PROTECTED]> wrote: > > On Feb 1, 2008, at 23:45, js wrote: > > > port search python shows me that every python2.5 port has prefix > > "py25" but that of 2.4 is only "py". > > If MacPorts would consider python2.4 is recommended python (due to > > some known problem) > > and called python2.4 port just "python", that would make sense, but > > ,unfortunately, it's not so. > > So IMHO using py24 prefix for 2.4 port would be more intuitive. > > > > What do you think of this? > > I' like to hear some comments on this and > > as a long-term goal, it would be nice to have a portnaming guildeline > > for python (or ALl ports across MacPorts project) > > The guideline is: use a numbered prefix if there's a good reason to. > A prefix was not used for the python 2.4 ports because there was no > python 2.5 at the time. Now there is, and I think it was just deemed > too much of a hassle to rename all the py-* ports to py24-*. > > _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-users
