[MacPorts] #39076: certsync @1.0.1 and curl-ca-bundle @7.30.0 should be marked as conflicting

[MacPorts]

#39076: certsync @1.0.1 and curl-ca-bundle @7.30.0 should be marked as conflicting
--------------------------------------+--------------------------------
  Reporter:  egall@…                  |      Owner:  macports-tickets@…
      Type:  defect                   |     Status:  new
  Priority:  Normal                   |  Milestone:
 Component:  ports                    |    Version:  2.1.3
Resolution:                           |   Keywords:
      Port:  certsync curl-ca-bundle  |
--------------------------------------+--------------------------------

Comment (by landonf@…):

 In the words of Highlander, "there can only be one". If we move forward
 with certsync, the curl-ca-bundle port will no longer be necessary. For
 now, certsync is experimental and (intentionally) conflicts with curl-ca-
 bundle:


 {{{
 port -f deactivate curl-ca-bundle
 port install certsync
 }}}


 There are a few options to make the CA handling more amenable to multiple
 certificate-providing ports; for instance, splitting curl-ca-bundle into
 individual pem files and populating the CA cert directory. However,
 certsync makes this moot, since it simply synchronizes the openSSL
 certificate store from the system keychain, which already has support for
 adding/removing CA certs and mixing the system roots with user and admin-
 installed certificates. In that regard, there's not any need to maintain a
 separate CA database.

-- 
Ticket URL: <https://trac.macports.org/ticket/39076#comment:2>
MacPorts <http://www.macports.org/>
Ports system for OS X