[MacPorts] #44494: p5.xx-modul -> is macports creating another "RPM" hell?

[MacPorts]

#44494: p5.xx-modul -> is macports creating another "RPM" hell?
-----------------------------+--------------------------------
 Reporter:  ora.et.labora@…  |      Owner:  macports-tickets@…
     Type:  request          |     Status:  new
 Priority:  Normal           |  Milestone:
Component:  base             |    Version:  2.3.1
 Keywords:                   |       Port:
-----------------------------+--------------------------------
 One of the charming aspects of MacPorts has been the avoidance of "RPM
 hells", i.e. there was -- at least in the past -- just on version of a
 tool installed and a simple upgrade kept the system up-to-date.

 Now, with versioning in place, we have to face for example:

 {{{
 $ port search p5.\*
 Found 5732 ports.

 p5.8-yaml @0.900.0 (perl)
     YAML loader/dumper module

 p5.10-yaml @0.900.0 (perl)
     YAML loader/dumper module

 p5.12-yaml @0.900.0 (perl)
     YAML loader/dumper module

 p5.14-yaml @0.900.0 (perl)
     YAML loader/dumper module

 p5.16-yaml @0.900.0 (perl)
     YAML loader/dumper module

 p5.18-yaml @0.900.0 (perl)
     YAML loader/dumper module

 p5.20-yaml @0.900.0 (perl)
     YAML loader/dumper module

 Found 7 ports.
 }}}

 Therefore a request for clarification whether McPorts is still in-line
 with it's original ideas? Why are we faced here with so many Perl
 versions?

-- 
Ticket URL: <https://trac.macports.org/ticket/44494>
MacPorts <http://www.macports.org/>
Ports system for OS X