Context Navigation

Changes between Initial Version and Version 1 of Ticket #40068, comment 4

initial	v1
8	8	> Uh, why? Users will already have the option to satisfy the dependency by manually installing curl-ca-bundle; there’s no reason to complicate the Portfile further.
9	9
10		`certsync` provides integration with the OS X keychain, if a user specifies that they want OS X keychain integration by selecting the relevant variant, and has neither `certsync` nor `curl-ca-bundle` installed yet, I would expect that MacPorts would pull in the port that better integrates with the keychain (i.e. `certsync`) to satisfy the depspec instead of the default `curl-ca-bundle`.
	10	`certsync` provides integration with the OS X keychain, if a user specifies that they want OS X keychain integration by selecting the relevant variant (`+osxkeychain` for larryv's branch ^(which is the default for `platform macosx`)^, or `-disable_keychain` for trunk), and has neither `certsync` nor `curl-ca-bundle` installed yet, I would expect that MacPorts would pull in the port that better integrates with the keychain (i.e. `certsync`) to satisfy the depspec instead of the default `curl-ca-bundle`. Conversely, if the user disables the keychain variant (`-osxkeychain` for larryv's branch, or `+disable_keychain` for trunk), that shows that the user is actively trying to avoid keychain-related stuff (perhaps, because they're on a platform other than `macosx` that doesn't use the keychain), so it would make sense that they would want to avoid `certsync` by having `curl-ca-bundle` installed for them instead.