On 3/22/15 10:35 AM, Lawrence Velázquez wrote:
On Mar 21, 2015, at 4:43 PM, Ryan Schmidt <[email protected]> wrote:
If you use "use_configure no", you're indicating to MacPorts that this port
uses something that isn't anything like autoconf, so that default universal variant goes
away, and you get to program one yourself.
This implies that "use_configure no" overrides "universal_variant yes". Would it make sense to
reverse this? That is, for an explicit "universal_variant yes" to create the universal variant, despite a
"use_configure no"?
vq
I was thinking along the same lines. You could even go one step further
and leave the default for universal_variant as yes even when
use_configure no is asserted but with an empty universal variant and no
configure (as the current port does) and allow the maintainer to assert
universal_variant no if necessary.
This would provide the same behavior as other ports (that do use
configure) but leaves the implementation of the universal variant to the
maintainer.
But I haven't looked at the base code to see what's really going on and
probably won't have time to do so for a while.
Dave
_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev
