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 more and more Rust. I think the only way around that is waiting for a binary package. —Mark _______________________ Mark E. Anderson <[email protected]> MacPorts Trac WikiPage <https://trac.macports.org/wiki/mark> GitHub Profile <https://github.com/markemer> On Sun, Nov 28, 2021 at 11:37 PM Kastus Shchuka <[email protected]> wrote: > Dear macports users, > > Recently, more and more ports began to depend on rust and cargo. > > Maybe rust is a wonderful language that will solve all problems of the > world. I just wonder, if it is so good, why it takes forever and a day > (literally) to compile? I've never seen anything taking that long to > build. > > I've been using graphviz port for over 10 years, I guess. I had to delete > it today. > > graphviz depends on gd2. gd2 depends on libheif. libheif depends on rav1e. > Now rav1e started depending on cargo-c, nasm, clang-13, cargo. > An attempt to upgrade rav1e launched a build of cargo-c which I had to > kill as I did not have luxary to wait for tens of hours for it to finish. > > I either have to keep outdated ports or stop using them and delete. > Unfortunately, the usable surface of macports started shrinking for me (or > should I call it "rusting"?). > > Another example is py-cryptography, which now requires rust to build. > Until binary package was made available, it took me over a day to upgrade > py-cryptography. > > I also now have a broken ImageMagic because its dependency chain pulls in > rust. And the list goes on and on. > > I doubt people who rushed rust into macports are going to reconsider their > decisions. I am just sharing my experience with this "rusting" > > Thank you for reading. > > -Kastus
