How to discontinue ports completely (py26 deprecation) ...
smithsp at fusion.gat.com
Wed Aug 10 11:23:20 PDT 2016
I am all in favor of removing cruft. However, would it be worthwhile to ping the user email list about the ports that will be deprecated (give a specific list), to see if anyone will complain, or is it better to just remove them, and then when someone complains tell them how to go back to an old version of a Port?
On Aug 10, 2016, at 11:18AM, Peter Danecek <peter.danecek at ingv.it> wrote:
> Hi all,
> In the process of deprecating `py26` subports, I am just looking at some very old python packages which were never moved to Python 2.7. It seems that in most cases there is a "good reason" why this did not occur. They are just not used anymore.
> Some of these packages are deprecated explicitly upstream in favour of substitutes. Sometimes the homepage or the sources can not be found found, or are extremely outdated. So rather than just keeping them alive in Macports (by moving them to Python 2.7 even if they build), I would propose to remove them completely.
> However, how would we procede in this case, when we have no explicit replacement to indicate?
> Just replace it by a stub?
> Just removing it the fast way?
> macports-dev mailing list
> macports-dev at lists.macosforge.org
More information about the macports-dev