*-graveyard ports retired

[Renee Otten]

If the conclusion is that replacements from, for example, py34-<something> to py35-<something> are not useful (as it appears from https://trac.macports.org/ticket/59051 <https://trac.macports.org/ticket/59051>) then this change seems fine to me. In that case we should recommend maintainers (likely in the guide or on the mailinglist) to just remove the value from “python.versions” when they want to remove a subport and be done with it.

If, on the other hand, the idea is that now every port needs to add the replacement rules in its own Portfile (as you did in the commit, but that might just be to retain the status quo), then I am not so sure about the removal of the py-graveyard port. I feel that would add unnecessary clutter to the Portfiles and we are likely better off keeping it centralized as it was before.

Renee


> On Sep 30, 2019, at 4:53 PM, Joshua Root <jmr at macports.org> wrote:
> 
> On 2019-10-1 06:44 , Mojca Miklavec wrote:
>> On Mon, 30 Sep 2019 at 22:36, Joshua Root wrote:
>>> 
>>> The p5-graveyard and py-graveyard ports have been removed as they no
>>> longer serve a useful purpose. The buildbot skips replaced ports
>>> automatically and thus doesn't generate the error reports that motivated
>>> the creation of the graveyards.
>> 
>> Why did you want error reports?
>> I thought the idea was to collect obsolete ports at a single place, so
>> that they would automatically get uninstalled.
> 
> The motivation was entirely that maintainers were getting failure
> messages from the buildbot about their obsolete subports every time they
> updated their portfile. It said as much in the long_descriptions.
> 
> - Josh

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20191001/6771db01/attachment.html>