ghc depends on perl 5.8 and perl 5.8 conflicts with perl 5.12

[takano32@…]

ghc depends on perl 5.8. perl 5.8 conflicts with perl 5.12.

i installed perl 5.12 and i cant install ghc on the way of this dependency.

does ghc really depend on perl 5.8 and cant install with perl 5.12?

i want use perl 5.12 and ghc in MacPorts.

thankyou.

[raimue (Rainer Müller)]

Additional variants +perl5_10, +perl5_12 would help.

[takano32@…]

Replying to raimue@…:

Additional variants +perl5_10, +perl5_12 would help.

thanks.

% sudo port install ghc-devel +perl5_12 
--->  Computing dependencies for ghc-develError: Unable to execute port: Can't install perl5.8 because conflicting ports are installed: perl5.12
To report a bug, see <http://guide.macports.org/#project.tickets>

hmm...

how can i use additional variants?

[jmroot (Joshua Root)]

As per the comment in the portfile, "only perl 5.8 is known to work reliably".

[takano32@…]

Replying to jmr@…:

As per the comment in the portfile, "only perl 5.8 is known to work reliably".

thanks.

[psarge@…]

According to the Darcs changelog on this file, it was fixed back in 2007 to work with Perl 5.9+. I expect the limitation is outdated.

Wed Jul 11 19:24:30 BST 2007 audreyt@…

• * Evil Mangler broke under Perl 5.9+ because $* is gone; this fixes it.

Perl 4's special variable $* controls multi-line matching; it's been deprecated from Perl 5's inception, and is finally removed in Perl versions 5.9 (soon to be 5.10).

Since GHC depends on Perl 5.6+ anyway, this patch introduces an equivalent effect to $* without using that special variable, by hooking into Perl's regex parsing process to add the /m flag.

Wed Jul 11 22:04:49 BST 2007 audreyt@…

• In mangler, lift the multiline-match pragma to toplevel and document it better.

Thu Jul 12 06:43:51 BST 2007 audreyt@…

• Revert the $* patch for earlier Perls as it breaks the build. Sorry. :/

Mon Jul 30 13:22:16 BST 2007 audreyt@…

• * ghc-asm: Finally did away with $* in a way that works with Perl 5.6~5.10+, by appending /m to all regexes.

[gwright@…]

I will check this out. If something other than the current port is required I will make a stripped down 5.8 just for ghc, with names changed so it doesn't conflict with the main port.

[ryandesign (Ryan Carsten Schmidt)]

Following the recent perl updates in r76485, the mangle_names variants have been deleted and their behavior made the default and only available option, thus perl5.8, perl5.10 and perl5.12 no longer conflict with one another. However, there is discussion of wanting to delete these separate-version perl ports and have just a single perl5 port at the latest version.

[danielluke (Daniel J. Luke)]

I think we could handle this like we do for most things.

Have perl5 be "the single perl5 port" that everything normally works with (and update it to 5.12.x). If ghc (or anything else) needs older perl, new ports just for those old versions can be created (or kept, in this case). If something needs older perl and a bunch of perl modules for that older perl, a port (or ports) for those modules would need to be created as well.