How install p5-libapreq2 for perl 5.20?

[Daniel J. Luke]

On Sep 15, 2014, at 5:23 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
> 
>> 
>> On Sep 15, 2014, at 4:16 AM, Mojca Miklavec wrote:
>> 
>> On Mon, Sep 15, 2014 at 4:19 AM, Ryan Schmidt wrote:
>>>> On Sep 14, 2014, at 9:43 AM, Murray Eisenberg wrote:
>>>> 
>>>> Can somebody tell me in simple terms how to go about installing p5.20-libapreq2?
>>>> 
>>>> I tried "sudo port install p5.20-libapreq2" but, as I already reported in a ticket, this gives during build the "usual" error:
>>>> 
>>>> info:build Can't locate ModPerl/MM.pm in @INC (you may need to install the ModPerl::MM module)
>>>> 
>>>> [Currently I have  p5.18-libapreq2 @2.130.0_3 installed, but also errors (report in a ticket) if I try to upgrade it to latest version.]
>>>> 
>>>> When I filed the ticket, it was closed as being a duplicate of #42582: p5-libapreq2: fails to build for any perl version except the default one (Can't locate ModPerl/MM.pm).
>>>> 
>>>> Is there some resolution?
>>>> 
>>>> Not being a macports developer or, for that matter, a perl developer -- just somebody who needs to use perl and perl modules within something else (WeBWorK) -- at this point I don't understand what to do.
>>> 
>>> We need to change the mod_perl2 port into a p5-mod_perl2 port that has subports for each perl version.
>> 
>> What is not clear to me is *how* to do that. It's clear about the
>> majority of files (perl modules), header files could be shared in a
>> separate package, but what would you do with
>> /opt/local/apache2/libexec/mod_perl.so
>> /opt/local/apache2/modules/mod_perl.so
>> ?
> 
> For the first iteration, I would do nothing special. I would let each subport install those files, which would make the subports conflict with one another. That's not desirable, but better than the current unworkable situation.
> 
> As a second iteration, I would try removing those files from the p5.*-mod_perl2 subports, and put only those files back into a mod_perl2 port. I assume mod_perl.so requires the rest of the perl-version-specific files, so that port would have perl5.* variants which depend on the corresponding p5.*-mod_perl2 port.

that mod_perl.so is version specific (ie, it would be different for each of the sub-ports and so it can't be pulled into one common port). The sub-ports would just have to be marked as conflicting.

It would be better if we just supported one perl5 version.
--
Daniel J. Luke                                                                   
+========================================================+                        
| *---------------- dluke at geeklair.net ----------------* |                          
| *-------------- http://www.geeklair.net -------------* |                          
+========================================================+                        
|   Opinions expressed are mine and do not necessarily   |                          
|          reflect the opinions of my employer.          |                          
+========================================================+