On Oct 11, 2018, at 12:29, Christopher Jones wrote:
>> Apparently, gcc48 can produce some zero-length N_SECTs that error out in the
>> default strip command but don't need to. Cameron made them warnings instead
>> (see below). We are reaching the limits of my knowledge about this issue
>> ri
On 10.10.18 04:09, Ryan Schmidt wrote:
Well, you could say that's also the purpose of the naming conventions we've used in other
portgroups. The naming of the github.setup procedure and the github.homepage option and
so forth are intended to convey that they are part of the github portgroup. I
> On 11 Oct 2018, at 6:51 pm, Ken Cunningham
> wrote:
>
>
> On 2018-10-11, at 10:38 AM, Christopher Jones wrote:
>
>> Hi,
>>
>> A couple other thoughts…
>>
>> What platforms do you see this being useful on ? I know that older
>> platforms, but newer than 10.4, also have issues with SSL/TL
On 2018-10-11, at 10:38 AM, Christopher Jones wrote:
> Hi,
>
> A couple other thoughts…
>
> What platforms do you see this being useful on ? I know that older platforms,
> but newer than 10.4, also have issues with SSL/TLS support. Presumably this
> would also be useful on these ? 10.6 ? 10.7
Hi,
A couple other thoughts…
What platforms do you see this being useful on ? I know that older platforms,
but newer than 10.4, also have issues with SSL/TLS support. Presumably this
would also be useful on these ? 10.6 ? 10.7 ?
Related to the above what is the rationale for forcing the use of
Hi,
> Apparently, gcc48 can produce some zero-length N_SECTs that error out in the
> default strip command but don't need to. Cameron made them warnings instead
> (see below). We are reaching the limits of my knowledge about this issue
> right about now …
OK. Looking at that patch, because al
On 2018-10-11, at 10:05 AM, Christopher Jones wrote:
> Hi,
>
> Being ’niche’ in itself is no reason to not include something in MacPorts, so
> that shouldn’t be a concern. We have plenty of ‘niche’ ports already, which
> is partly what makes MacPorts better than the alternatives ;)
>
> If t
Hi,
Being ’niche’ in itself is no reason to not include something in MacPorts, so
that shouldn’t be a concern. We have plenty of ‘niche’ ports already, which is
partly what makes MacPorts better than the alternatives ;)
If the new ports build ‘normally’ like any other, then why not have them i
Older MacOS versions lack browsers that support TLSv1.2, and other enhancements
that allow them to work comfortably in the current world. Cameron Kaiser has
been dutifully maintaining a fork of Firefox for a decade that works nicely on
PPC Macs 10.4 and 10.5, and keeps it remarkably up to date w
