On 18 Oct 2014, at 17:45, Ryan Schmidt <ryandes...@macports.org> wrote:
> >> On Oct 18, 2014, at 9:19 AM, p...@macports.org wrote: >> >> Revision >> 126965 >> Author >> p...@macports.org >> Date >> 2014-10-18 07:19:30 -0700 (Sat, 18 Oct 2014) >> Log Message >> >> py-mssql: update to 2.1.0, remove py24, py25 subport > > Perhaps we want to add them to py-graveyard? Maybe, was considering this, but I am not really sure. This is not really related to the deprecation process. The situation here is rather comparable to what we did earlier when updating ports and older Python versions were not supported. But on the other hand, adding this to py-graveyard should not have any drawback and might even provide a smoother user experience. I understood, that the new subport (here: py27) should be already around when adding to py-graveyard. So this always needs to be a two step process. But keeping the unsupported subport(s) around when updating makes no sense. Right? Should I add I now? ~petr _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
