I think this is more a reflection of the open source landscape than
anything we're doing.
py-cryptography, for example, is 8% Rust, according to Github. I don't know
when they added it, but the latest version needs it. Same goes for rav1e.
It's one-third Rust.
Along with Go, you're going to see m
It is _possible_ to write reliable, secure code in C or even assembler. But for
large complex software, it's darn unlikely; there's too many ways to mess up,
even for capable and meticulous programmers, and most, even if bright and
useful, aren't _that_ good.
Rust is supposed to eliminate a num
Give the developers of rust itself a piece of your mind if you like,
over how slow it is to compile. Good luck with that - I suspect to be
THAT slow (although really? compiling a C compiler suite plus library
isn't exactly fast either) they might be doing some things by brute
force that they
On 2021-11-29 at 08:32:46 UTC-0500 (Mon, 29 Nov 2021 13:32:46 +)
Chris Jones
is rumored to have said:
If you find yourself during an port update building rust from source,
either just let it finish, or if you don't want your machine tied up
building rust for some period, just cancel the bu
I would expect that the buildbots also need to satisfy dependencies, and thus,
heavily-depended on builds would tend to be done earlier, regardless of whether
or not they were large and slow; and if they are large and slow, they're
arguably delaying the building of even more smaller ports that d
This looks as the same problem we have with MySQL57, where it's using
the system cctools instaead of the more modern cctools from macports.
The fix is described here :
https://trac.macports.org/ticket/59072#comment:1
declare usrBin='/usr/bin'
declare devBin="/Developer${usrBin}"
while read -u 9
To first order builds are done on a first-committed-first-built basis.
The time a build takes is not something known up front so prioritizing
basis on this would anyway not really be feasible.
Yes, the builders must install the dependencies of a port before a given
port can be built. If one
Well, I wonder whether someone did something within the last day or two.
I just tried it again, and lo-and-behold, perl5.26 installed just fine &
now MacPorts is getting to work on the backlog of things that I could
not update because of this problem.
This after I just found out (in debug mode
