<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">[sorry for the delay, picking this up again post-holidays]<div><br><div><div>On Nov 29, 2013, at 3:38 , Ryan Schmidt <<a href="mailto:ryandesign@macports.org">ryandesign@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">I’ve switched many of my MacPorts installs to certsync, including on Leopard, but I don’t know if it’s working correctly (how would I test that?).</span></blockquote><div><br></div><div>As long as you're getting a populated cert file, you're set.</div><br><blockquote type="cite"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;"> Unfortunately certsync fails to build on Tiger; I would love to get that fixed.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></blockquote><div><br></div><div>What are the errors you're hitting? I don't have a Tiger install to work with locally, but in theory I could try to bring it up in VMware.</div><br><blockquote type="cite">The problem with leaving curl-ca-bundle intact and leaving ports using the path:-style dependency is that all existing users of MacPorts would continue to use curl-ca-bundle unless they manually intervened. If certsync is working properly, it would be nice to automatically switch all users to it (i.e. make curl-ca-bundle replaced_by certsync). That’s going to get tricky if we have to make exceptions for older OS versions.</blockquote></div><br></div><div>I'd be fine with that; let's sort out the OS compatibility and get it working across the board.</div><div><br></div><div>-landonf</div></body></html>