[107013] trunk/dports/devel

[Adam Mercer]

On Mon, Jun 17, 2013 at 4:07 AM, Dennis van Dok <dennisvd at nikhef.nl> wrote:

>> Dennis: You're more familiar with globus than I am, what do you think
>> is the best way to address this?
>
> I agree this isn't right. Much of this is due to way the Globus build system
> tries to deal with portability.
>
> There are a few globus packages that install perl stuff:
> globus-common, which installs ${perlmoduledir}/Globus/Core/{Config,Paths}.pm;
> grid-packaging-tools, which installs .../Grid/GPT/*
> globus-gram-*, for .../Globus/GRAM/*
>
> It looks like the ${perlmoduledir} is almost exactly what ${perl5.lib}
> (or ${perl5.archlib}) would be when using the perl5 PortGroup. Can we
> somehow use ${perl5.lib} without all the side-effects of the perl5
> PortGroup?

Probably not, the best thing is to may be to simply set a variable
equal to value of ${perl5.lib} and then use that.

> In any case globus-core seems to hardcode the perl module path,
> so unless this is patched (I don't know how, yet) we will end up
> having to hardcode this in the Portfile anyhow.

Can you take a look at this?

Cheers

Adam