What is perfectly doable, done in fact with many ports (including the discussed
one), and IMO should be done – provide fallbacks whenever the latest version is
unfixable for the older systems.
Of course, it is an open source project, and what is actually done is
conditional on good will and
On 11/10/2023 06:25, Perry E. Metzger wrote:
That said, I presume there's a strong overall consensus that on current
hardware, we run the current (supported) versions of software, and that
older operating systems and hardware are supported only on a "if it
doesn't hurt anything" basis.
The
>
> That said, I presume there's a strong overall consensus that on current
> hardware, we run the current (supported) versions of software, and that
> older operating systems and hardware are supported only on a "if it doesn't
> hurt anything" basis.
>
I'm not sure this is 100% accurate, either.
And Mascguy didn't seem to care to explain the situation, which I
clearly didn't understand. Okay, That makes more sense and is acceptable.
That said, I presume there's a strong overall consensus that on current
hardware, we run the current (supported) versions of software, and that
older
In general terms I (who am absolutely nobody) agree with you, but there's one
thing I believe you're not taking into account and it's that this is a fallback
version for users with ancient hardware.
The main `librsvg` port is currently at `2.56.3`, which was released two months
ago
@Chris, I
Hi,
I am not sure what you are complaining about. Version 2.56.3, whilst not the
absolute latest version a pretty up to date rust based version, is already used
on Darwin 10 and newer. Your mail below seems to imply the old C version is
used everywhere, which just isn't the case. What am I
See the following thread:
https://github.com/macports/macports-ports/pull/20744 — but to
summarize, Mascguy does not want to update librsvg to a safe / modern
one because ancient versions of MacOS can't support Rust.
So I don't want to be a pain in the neck, but I have little interest in
Could someone who understands what mpbb scripts are doing address this?
https://trac.macports.org/ticket/68408
We got numerous R ports broken by this on CI. (Locally everything works
fine, buildbot apparently too.)
I can’t keep updating R ports unless this is fixed. It is too much of a
