problem generally on SL is the trickle of creeping C++11
dependencies that have made it essentially mandatory to do this:
https://trac.macports.org/wiki/LibcxxOnOlderSystems and then hack around
breakage in ports like lz4 that blindly ignore the MacPorts tweaks that
can allow them to build.
--
Bill
wly and even many core modules are maintained independently such that
updated versions can be installed on "end of life" Perl versions. This
is intrinsically difficult to fit into a package management system using
an orthodox conceptual model of versions and dependencies.
--
Bill Cole
b...@s
On 19 Jan 2018, at 11:09, Richard L. Hamilton wrote:
On Jan 19, 2018, at 09:53, db wrote:
[...]
But since this is MacPorts, I wonder if anyone has had problems
specifically with a port not working and crashing.
At a mere guess, I'd say there'd be very little of that.
On 19 Jan 2018, at 8:44, Jan Stary wrote:
On Jan 19 06:48:37, rlha...@smart.net wrote:
[...]
but for backwards compatibility with macOS's pre-Unix ancestors,
Huh. What are those?
Not technically "pre-Unix" but rather "pre-MacOS X." MacOS X (i.e. 10.0)
was the first version derived from
On 9 Jan 2018, at 10:30, Daniel J. Luke wrote:
On Jan 8, 2018, at 9:46 PM, Bill Cole
<macportsusers-20171...@billmail.scconsult.com> wrote:
An issue with that is the fact that some amount of perl5 code in the
wild (often including widely-used non-core modules) is broken with
each
ial attention beyond a
simple 'port upgrade.' The advantage of an aggregated log of such
changes like the UPDATING file is that it enables a project-wide policy
on what should be noticed and how far back to retain old notices, and it
would keep ever-growing records of change out of Portfiles.
-
On 4 Jan 2018, at 4:53, Ryan Schmidt wrote:
On Dec 30, 2017, at 20:27, Bill Cole wrote:
[...]
If anyone involved in making MacPorts policy can explain this
coherently, I'd greatly appreciate it.
What other explanation would you like?
Well, I'm not entirely sure...
I think I've figured
On 1 Jan 2018, at 14:55 (-0500), Craig Treleaven wrote:
On Dec 31, 2017, at 11:46 PM, Bill Cole
<macportsusers-20171...@billmail.scconsult.com> wrote:
Ah, so apparently the reason this met total silence was that it got
lost/dropped somewhere so only I thought it was posted. Odd...
Re
r, which was Apple's first MacOS X replacement for init)
plus inetd, as well as an alternative to crond. It is what Linux systemd
should have been: a unified supervisor and scheduler that doesn't rely
on a bunch of shell scripts of diverse quality.
--
Bill Cole
b...@scconsult.com or billc...@ap
deprecation
here: https://developer.apple.com/documentation/quartz
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Currently Seeking Steady Work: https://linkedin.com/in/billcole
Ah, so apparently the reason this met total silence was that it got
lost/dropped somewhere so only I thought it was posted. Odd...
Reposted message:
From: Bill Cole <macportsusers-20171...@billmail.scconsult.com>
To: macports-users@lists.macports.org
Subject: What's the push to r
On 15 Dec 2017, at 18:00 (-0500), Bill Cole wrote:
In regards to https://trac.macports.org/ticket/55208 :
[...]
Why would help2man demand the absolute latest Perl? Well, because the
Portfile says it does. However, in the real world, help2man is happy
with any perl since 5.8.
Doing a 'port
201 - 212 of 212 matches
Mail list logo