fetch ssl errors on _some_ buildbots

[Rainer Müller]

On 2015-03-22 23:19, Mihai Moldovan wrote:
> On 22.03.2015 11:07 PM, Rainer Müller wrote:
>> On 2015-03-22 20:47, Ryan Schmidt wrote:
>>> We should totally ship a newer version of curl and openssl or gnutls with MacPorts, like we already ship a version of Tcl.
>>
>> I don't think it is worth to invest resources into this. The usual
>> policy is to support the latest two releases of OS X. Any release older
>> than OS X 10.9 Mavericks should be considered legacy.
> 
> So... what's the best way to deal with issues like this one? Ignore
> them? Change the fetch type to HTTP if possible? (Note: this may not be
> supported by all servers -- for instance because they are automatically
> redirecting to HTTPS. I've personally set up a few (sub-) domains in
> that vain.) Manually mirror the distfiles? (I don't even know if it's
> currently possible to manually upload distfiles.)

For ports I maintain, I will not work on issues that affect legacy OS X
releases only. If someone still uses such an old system and wants to
continue to use it, I am glad to accept a patch and apply it. However, I
will not invest time and effort to find a solution. Exceptions might
apply for trivial changes or for other reasons such as personal involvement.

While we do not have this as a written policy, I think it is reasonable
and also handled by other maintainers in a similar way.

Rainer