subversion-perlbindings: Subports conflict on libsvn_swig_perl-1.0.dylib

[raimue (Rainer Müller)]

I have subversion-perlbindings-5.16 installed and tried to install git-core +svn, which needs p5.12-svn-simple and that requires subversion-perlbindings-5.12. The installation resulted in the following error:

--->  Activating subversion-perlbindings-5.12 @1.7.8_2
Error: org.macports.activate for port subversion-perlbindings-5.12 returned: Image error: /opt/local/lib/libsvn_swig_perl-1.0.dylib is being used by the active subversion-perlbindings-5.16 port.  Please deactivate this port first, or use 'port -f activate subversion-perlbindings-5.12' to force the activation.
Error: Failed to install subversion-perlbindings-5.12

It should either be possible to install these ports side-by-side or they need to be marked conflicting.

[danielluke (Daniel J. Luke)]

They probably need to be marked as conflicting (I think many/most of the p5 versioned ports conflict already though, if only because they try to install the same man pages...)

[cooljeanius (Eric Gallager)]

Replying to dluke@…:

(I think many/most of the p5 versioned ports conflict already though, if only because they try to install the same man pages...)

Really? I've been able to get away with installing my perl ports with a wildcard instead of a version number for the most part...

[danielluke (Daniel J. Luke)]

Most of the p5.xx ports conflict with their p5.xx alternatives (or at least they did the last time I checked). In this case, git-core probably needs variants for perl5.16.

It does make sense that the subversion-perlbindings port should be fixed to either allow multiple version installation or have the versions marked as conflicting - but I think this may be a general issue with the p5 ports.

This really would all be simpler if we just chose one perl version and optionally had older versions around (without p5 modules installing for them) ... I still don't think there's a compelling reason to support anything other than the most recent perl5.

[larryv (Lawrence Velázquez)]

Replying to dluke@…:

Most of the p5.xx ports conflict with their p5.xx alternatives (or at least they did the last time I checked).

jmr fixed this in r94655.

This really would all be simpler if we just chose one perl version and optionally had older versions around (without p5 modules installing for them) ... I still don't think there's a compelling reason to support anything other than the most recent perl5.

+1

[danielluke (Daniel J. Luke)]

conflicts added in r104067

If someone else wants to figure out how to make everything happy and be able to install multiple versions simultaneously, I wouldn't be apposed to applying a patch.