<div dir="ltr">Hi all,<div><br></div><div>It seems to me that as of recently it was the case that variants from the install command line are passed on to the building of dependencies (as discussed below last year), but that it is no longer happening. Is this something that was changed (deliberately or otherwise) in the 2.3.4 release?</div><div><br></div><div>Specifically, my recently added xcrysden port needs tk +x11 (checked via active_variants), whereas the default is +quartz. As of a couple of weeks ago, I think I was able successfully to trigger installation of tk +x11 when it was not installed by doing 'port install xcrysden +x11'. But now this doesn't happen.</div><div><br></div><div>Another question related to active_variants: would it be possible for require_active_variants to perform its check not just in the pre-configure phase as is currently the case, but also in the activate phase? Currently, you could install xcrysden when tk +x11 was active, then deactivate xcrysden, install tk +quartz, and re-activate xcrysden. It would no longer work. It would be good if we could write an error at this point. I tried adding code to pre-activate to accomplish this, but I found it was only called when doing a fresh install, not when activating a deactivated port. Is there a way to get some code to run when activating a deactivated port?</div><div><br></div><div>Thanks,</div><div>David<br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Nov 16, 2014 at 6:40 PM, Lawrence Velázquez <span dir="ltr"><<a href="mailto:larryv@macports.org" target="_blank">larryv@macports.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Nov 16, 2014, at 5:32 PM, David Strubbe <<a href="mailto:dstrubbe@macports.org">dstrubbe@macports.org</a>> wrote:<br>
<br>
> All right, but can you clarify about default variants: is it true that default variants are not passed to dependencies, but all other variants are? And, is there any good reason for this? It would solve my problem immediately if they were passed on.<br>
<br>
</span>As far as I know, variants are only passed from the command line, and even then they are only applied when dependencies have to be installed. Running<br>
<br>
port install foo<br>
<br>
where foo has some default variant +bar is *not* equivalent to running<br>
<br>
port install foo +bar<br>
<br>
I don't know the reason for this behavior.<br>
<br>
vq</blockquote></div><br></div></div></div>