[MacPorts] #50000: perl5: improve / reimplement packaging

[MacPorts]

#50000: perl5: improve / reimplement packaging
-----------------------------+--------------------------------
  Reporter:  mojca@…         |      Owner:  macports-tickets@…
      Type:  enhancement     |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:
Resolution:                  |   Keywords:
      Port:  perl5 perl5.22  |
-----------------------------+--------------------------------

Comment (by rjvbertin@…):

 As long as the perl5 and p5-foo ports remain around I presume nothing much
 will change except for ports that

 - depend on binary content in a p5- port - those ports will probably need
 more attention by their maintainer
 - ports that for some reason don't work with a newer perl version. I'm not
 sure what you'd do with those anyway.

 However, I'd strongly suggest to develop something (a script, to be
 installed by the main perl5 port?) which allows to update/upgrade only the
 perl install. Regular users should probably still keep running the usual
 `port selfupdate && port upgrade outdated` sequence, but there should be
 something for advanced users who live on the edge too. Maybe that
 something would be as simple as a `port upgrade perl5` followed by a loop
 that upgrades all installed `p5-*` ports, but ideally there would also be
 some logic in place to fetch new Portfiles selectively.
 This could also be a specific port; that would allow the perl port devs to
 push tested versions of the updating script, when they're ready, either
 through an upgrade of that port, or through an independent download.

 In light with those last thoughts: selective updating would probably be
 easier if all perl portdirs were moved into a dedicated subdirectory so
 one could do something like `(cd `port dir perl5`/.. ; svn up)`.

 Another approach I'm testing with my own KF5 ports: specify the current
 version (and possibly a "latest" version) in the PortGroup which all ports
 providing perl-related things are supposed to include anyway (unless that
 messes up the configure.cmd, build.cmd etc, like the Python PortGroup
 does?). It seems to work, though I have occasional ports that don't pick
 up a version upgrade after running portindex.

 Mojca also asked for out of the box thinking: what if the p5- ports simply
 tapped into existing CPAN functionality?

-- 
Ticket URL: <https://trac.macports.org/ticket/50000#comment:16>
MacPorts <https://www.macports.org/>
Ports system for OS X