Hi,
On 30.04.2014, at 10:26, Ryan Schmidt wrote:
> The plan was to default to certsync after the problems had been ironed out,
> and for a brief time, they were, but then an update to certsync made it
> incompatible with Leopard and Tiger, and since it synchronizes with the
> system certifica
Hi,
On 30.04.2014, at 09:45, mk-macpo...@techno.ms wrote:
> I am not sure whether it had been already said, but I think it would be nice
> to let query list also generate links to the port’s home URL, which holds
> just as well for the MacPorts port list!
Patches welcome, I guess? The source i
On Apr 30, 2014, at 02:42, and.dam...@macports.org wrote:
> Revision
> 119549
> Author
> and.dam...@macports.org
> Date
> 2014-04-30 00:42:17 -0700 (Wed, 30 Apr 2014)
> Log Message
>
> port weechat: switch to certsync rather than curl-ca-bundle as default CAs
> provider, #43512
> Modified Paths
I am not sure whether it had been already said, but I think it would be nice to
let query list also generate links to the port’s home URL, which holds just as
well for the MacPorts port list!
___
macports-dev mailing list
macports-dev@lists.macosforge.o
On Sun, Dec 22, 2013 at 7:34 PM, Landon Fuller wrote:
> If things look good to everyone, I'd like to move all ports over to using
> certsync as a certificate store, replacing curl-ca-bundle.
While doing so can we agree to rely $prefix/etc/openssl/cert.pem for
the CAs rather than pointing at share
