> That's the current implementation. Ryan's point is that logically
> 'pdf' should be a superset of 'html', so I am trying to accommodate
> that request.
In that case you'd do a requires.
variant X requires variant Y description { ... }
Inside the logic, the +html variant should continue to rem
On Nov 12, 2010, at 15:24 , Jeremy Lavergne wrote:
[…]
>>
>> How would the "grayer beards" than mine of MacPorts suggest I tackle
>> Ryan's suggestion?
>
> You might simply set the two variants as conflicting.
>
> variant X conflicts Y description {Z} { ... }
That's the current implementatio
> Logically I agree that your request makes sense, but I need some
> conceptual help here due to my limited knowledge of Portfiles. The
> 'html' variant works by patching the SBCL source to not install the
> full documentation. The 'pdf' variant needs this code not to be
> patched to execute. I
On Nov 2, 2010, at 01:45 , Ryan Schmidt wrote:
[…]
> It sounds like the pdf variant does everything the html variant
> does, and then a little more. So why not make the pdf variant require
> the html variant, instead of making them conflict? Especially since
> the html variant is selected by def
On Nov 1, 2010, at 11:59, easie...@macports.org wrote:
> Revision: 73027
> http://trac.macports.org/changeset/73027
> Author: easie...@macports.org
> Date: 2010-11-01 09:59:42 -0700 (Mon, 01 Nov 2010)
> Log Message:
> ---
> Make '+pdf' and '+html' mutually exclusive
>
> Mo
