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

MacPorts noreply at macports.org
Mon Dec 21 15:20:35 PST 2015


#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  |
-----------------------------+--------------------------------
Description changed by mojca@…:

Old description:

> I'm opening this ticket to collect and vote on ideas with their pros and
> cons about different options to package:
>   * `perl5[.x]`
>   * perl modules `p5[.x]-foo`
>   * ports that depend on Perl
>   * `perl6`
>
> Desired features:
>   * easy updates of perl modules, possibly (semi-)automated from metadata
> from CPAN
>   * painless upgrades from `perl5.[n]` to `perl5.[n+1]`
>   * reasonably small effort with modifying and revbumping all the ports
> that depend on Perl
>
> Some particular aspects to think about:
>   * a port could have a flag (possibly "auto-generated") to indicate that
> there is no difference in what Perl version is being used (other than
> maybe path to perl, but path could be version-neutral); those ports won't
> need any revbumps after changing the version
>   * ...
>
> Please try to think out of the box and and come up with proposals even if
> implementing them is not yet supported by the base. We can extend the
> base if we know exactly what we want to achieve.
>
> (No need to rush into any decisions and implementations before we
> carefully think of all the consequences of that particular
> implementation.)

New description:

 I'm opening this ticket to collect and vote on ideas with their pros and
 cons about different options to package:
   * `perl5[.x]`
   * perl modules `p5[.x]-foo`
   * ports that depend on Perl
   * `perl6`

 Desired features:
   * easy updates of perl modules, possibly (semi-)automated from metadata
 from CPAN
   * painless upgrades from `perl5.[n]` to `perl5.[n+1]`
   * reasonably small effort with modifying and revbumping all the ports
 that depend on Perl

 Some particular aspects to think about:
   * a port could have a flag (possibly "auto-generated") to indicate that
 there is no difference in what Perl version is being used (other than
 maybe path to perl, but path could be version-neutral); those ports won't
 need any revbumps after changing the version
   * ...

 Please try to think out of the box and and come up with proposals even if
 implementing them is not yet supported by the base. We can extend the base
 if we know exactly what we want to achieve.

 Some relevant tickets that have been open for a long time already:
   * [[TicketQuery(id=29763|36980|43741)]]

 (No need to rush into any decisions and implementations before we
 carefully think of all the consequences of that particular
 implementation.)

--

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


More information about the macports-tickets mailing list