dear Ryan, thank you for keeping a close eye on things, especially useful for newbies like me who try to do the correct thing but not always succeed...
> On May 25, 2018, at 3:48 PM, Ryan Schmidt <ryandes...@macports.org> wrote: > > Replacement doesn't work (doesn't show up in "port outdated") unless the > version or revision of the replacement is higher. So you want "0.7.6_1" here, > to be higher than the 0.7.6_0 (version 0.7.6 revision 0) in the py-alabaster > port. > > The same goes for other ports you've obsoleted recently: py-snowballstemmer, > py-pkgconfig. > > Please keep the list of ports in the py-graveyard port sorted in alphabetical > order. I looked at some examples and thought I understood how to do it, but apparently not. Just to make sure I get it now, let’s consider the imaginary “py-port” that is at version 1.0 (revision line not present) and the two following situations: 1. obsolete subport py26 without a newer version I remove the py26 subport from the py-port Portfile and add “py-port 1.0_1 26” to py-graveyard. Do I need to increase the revision in the py-port Portfile as well or not? 2. obsolete subport py26 and at the same time update the version to 1.1 I remove the py26 subport from the py-port Portfile, update it to the latest version, and add “py-port 1.1 26” to py-graveyard. Is that how it’s supposed to be done? Sorry about the alphabetical order, I will correct that at the same time. Thanks, Renee
