On Apr 6, 2015, at 3:47 AM, René JV Bertin wrote:
>
> On 06 Apr 2015, at 04:42, Lawrence Velázquez wrote:
>
>> https://trac.macports.org/wiki/PortfileRecipes#deactivatehack
>
> I'm quite certain I could have used recipes from that page (e.g. to
> deactivate the 'standard' port when installing/a
Yes, that will work. I had seen the "deactivate hack" in some other
ports, but didn't see a way to check for "contents". Moving that check
to a version check will work. Thanks - MLD
On Sun, Apr 5, 2015, at 10:42 PM, Lawrence Velázquez wrote:
> Sounds like you actually want the deactivate hack.
>
On 06 Apr 2015, at 04:42, Lawrence Velázquez wrote:
>
> https://trac.macports.org/wiki/PortfileRecipes#deactivatehack
I'm quite certain I could have used recipes from that page (e.g. to deactivate
the 'standard' port when installing/activating the -devel version).
Did I miss a pointer to th
On Apr 5, 2015, at 9:56 PM, Michael Dickens wrote:
> Thus, in the new volk Portfile, I need to set up a pre-extract check to
> see if libvolk is already installed, and if so then which port owns it.
> If a gnuradio* port owns it, then I have the Portfile error out, telling
> the user to force dea
I'm in the process of splitting of a project (volk) from a port
(gnuradio); until last week they were provided in the same repo, and now
they are provided as 2 separate repos (but, volk is still required to
build gnuradio). This split is currently for gnuradio-(devel,next) only;
the release will ca
