Vincent Habchi writes:

> Le 24 août 2014 à 18:53, Sean Farley <s...@macports.org> a écrit :
>
>> Why not use the bitbucket port group?
>> 
>> PortGroup           bitbucket 1.0
>> bitbucket.setup     petebunting rsgislib 52fb22e
>> version             0.0.20140822
>
> Uh, I tried that and it works (fetch okay), but then I have a problem.
>
> The fetch creates a subdirectory ‘52fb22e' under ‘work’ and in this 
> subdirectory, I find the ‘trunk’ directory which contains the code. Now if I 
> try to modify worksrcdir to point to ‘52fb22e/trunk’, then the fetch is 
> placed under this new arborescence rather than directly under ‘52fb22e’, so 
> the code is now in ‘52fb22e/trunk/trunk’. Etc. Sounds like the bitbucket port 
> uses ‘worksrcdir’ to create the directory in which to store the code. Any 
> workaround?
>
> Vincent

There are a few ways to work around this. In the dolfin port, I do:

configure.dir       ${worksrcpath}/build
build.dir           ${worksrcpath}/build

You could try changing the worksrcpath but I don't know if that would
work. Or maybe just changing the worksrcdir in a different phase.
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to