[MacPorts] #59051: Remove *-graveyard ports

MacPorts noreply at macports.org
Sat Sep 21 12:57:00 UTC 2019


#59051: Remove *-graveyard ports
----------------------------------------+--------------------
  Reporter:  jmroot                     |      Owner:  (none)
      Type:  enhancement                |     Status:  new
  Priority:  Normal                     |  Milestone:
 Component:  ports                      |    Version:
Resolution:                             |   Keywords:
      Port:  py-graveyard p5-graveyard  |
----------------------------------------+--------------------

Comment (by mojca):

 I understand the pain being present with the python graveyard ports.
 For perl we try to keep this minimal and only update the graveyard once or
 twice per year which seems like a reasonable compromise to allow getting
 rid of the gazillion of no-longer-existing subports.

 Also, perl is somewhat special in the way that we do have the `perl5`
 port, so to some extent and with quite a bit of limitations the intention
 does work to some extent (when we upgrade perl5 to use a newer version and
 remove the old variant, and if we removed the old subports at the same
 time, modules that previously worked with perl might keep working). So
 maybe this is a plea to keep the p5-graveyard if you happen to decide to
 remove the other one.

 For python ... could we at least provide a mechanism to remove old ports?
 I agree that the py-graveyard has very very limited usability, and by
 constantly updating it just for the sake of one port at a time, given the
 waaaaaaay to long parsing time of the file, it's a bit of annoyance.

-- 
Ticket URL: <https://trac.macports.org/ticket/59051#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list