On 17.11.2014 11:14 am, Rainer Müller wrote: > This will definitely break if someone already installed pinentry, but > then gets a pre-compiled archive of gpg-agent from our buildbot which > expects pinentry-mac.
Ok, that's a valid point. > > You should make this selectable with a variant +pinentry_mac, which then > could be selected by default on the appropriate OS X versions. Yeah, so the same logic but with a variant, preventing binary archives to be fetched pinentry-mac is not selected. Sure thing, will do. -- What this logic does is simulate a bin/lib:-style dependency with more constraints. bin:pinentry:pinentry-mac probably does the same, if I'm not totally mistaken, but I don't like that, as pinentry-mac doesn't actually install a pinentry program in any bin path. I also need to know which port has been selected as a dependency for the configure flag. The configure flag is merely hardcoding the path to pinentry as the default to look for. Users can and SHOULD[RFC] always override this via ~/.gnupg/gpg-agent.conf to make sure they get what they want. It's not critical. Mihai _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
