[126965] trunk/dports/python/py-mssql

petr 976F at ingv.it
Sat Oct 18 09:21:22 PDT 2014

On 18 Oct 2014, at 17:45, Ryan Schmidt <ryandesign at macports.org> wrote:

>> On Oct 18, 2014, at 9:19 AM, petr at macports.org wrote:
>> Revision
>> 126965
>> Author
>> petr at 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?

More information about the macports-dev mailing list