News for hackers. Stuff that matters.
Re:Cargo: predictable dependency management by Gankro on Thursday May 05, 2016 @04:06PM (#11639283)
Happier than Rust 1.0 and the end of The Rustup?
Re:Cargo: predictable dependency management by cm3 on Thursday May 05, 2016 @05:16PM (#11639719)
End of The Rustup? AFAICS, it's still downloading a very specific servo-only rustc.
Re:Cargo: predictable dependency management by mbrubeck on Thursday May 05, 2016 @06:04PM (#11639999)
It downloads a regular Rust nightly build these days. It depends on the specific nightly date (because we use compiler plugins that link to unstable rustc internals), but at least we no longer have to build our own Servo-specific snapshots.
Re:Cargo: predictable dependency management by kibwen on Thursday May 05, 2016 @05:44PM (#11639875)
Servo's efforts to upgrade their version of rustc used to be legendarily traumatic, these days it's comparatively tame. :)
Re:Cargo: predictable dependency management by cm3 on Thursday May 05, 2016 @05:49PM (#11639904)
Right, and if the binary toolchains would be built with musl (not targeting musl) statically, we could have a rustc+cargo that works on both glibc and musl, avoiding two versions.
Re:Cargo: predictable dependency management by dbaupp on Thursday May 05, 2016 @10:07PM (#11641196)
Could you explain what you're referring to? It seems like a total non sequitur, since as far as I know, there has never been any pain (or even rumour of pain) in a Rust upgrade caused by what libc the compiler uses, but rather breakage in the unstable features that servo uses.
Re:Cargo: predictable dependency management by cm3 on Friday May 06, 2016 @08:36AM (#11643503)
If the official rust+cargo was built statically with musl, then a single download would work on glibc and musl distros. Right now, we don't have a download that works on musl, and one has to bootstrap on a glibc system, targeting musl, which makes it impossible to bootstrap rust+cargo on a musl distro without glibc because bootstrapping requires a snapshot.
Re:Cargo: predictable dependency management by dbaupp on Saturday May 07, 2016 @07:10AM (#11649146)
Ah, it is a total non sequitur, unrelated to what servo encounters when changing Rust versions?
Re:Cargo: predictable dependency management by cm3 on Saturday May 07, 2016 @12:41PM (#11650242)
I don't understand what you're saying. I suggested that linux builds of rust+cargo ought to be done as musl-static (not for targeting musl) so that a single download works on both Ubuntu and Alpine. Now we have only glibc builds. Yes, it's not related to servo, but it is relevant to you mentioning glibc, though this is off-topic so let's stop arguing.
Re:Cargo: predictable dependency management by dbaupp on Saturday May 07, 2016 @07:05PM (#11651775)
I think you should go back and re-read the conversation, particularly kibwen's comment above and your reply: they seem to be totally unconnected. I was trying to understand how you thought they (Servo upgrading Rust versions and a musl-compiled rustc) were related, I was not arguing. There is in fact no mention of glibc until your comments, nor is there any implication in my comments that I don't understand what musl does nor do I disagree that it is useful (in fact, I used Rust's easy ability to link binaries against musl just a few days ago). This discussion is purely prompted by me trying to understand why you thought it made sense to talk about musl on a seemingly unrelated comment... maybe there was some insightful connection I missed, but it seems not.
Re:Cargo: predictable dependency management by cm3 on Saturday May 07, 2016 @07:34PM (#11651869)
You're right.
Re:Cargo: predictable dependency management by cm3 on Thursday May 05, 2016 @08:52PM (#11640906)
I really wish downvotes would require a comment so that I knew why the two posts in this thread branch went negative after being positive for a long time. I feel like people treat it like a personal spam filter although it's the same view for everybody. Odd.