Announcing the new Rust package manager, Cargo

Re:Announcing the new Rust package manager, Cargo by davidgerard on Tuesday March 18, 2014 @08:48AM (#7421527)

Every application expands until it contains a sketchy rewrite of apt-get.

I BEG YOU as a sysadmin: make sure this stuff is compatible with Debian packaging. Please. Please.

[ Parent | on HN ]

Re:Announcing the new Rust package manager, Cargo by byroot on Tuesday March 18, 2014 @09:07AM (#7421619)

I don't know much about Rust, but AFAIK it's mostly static linking like Go. So 2 Rust applications won't have to share anything, so developments packages do not have to be converted into deb packages. Unlike ruby or python packages.

[ Parent | on HN ]

Re:Announcing the new Rust package manager, Cargo by davidgerard on Tuesday March 18, 2014 @09:27AM (#7421731)

I fear it'll be one of those things where "can" becomes "must".

[ Parent | on HN ]

Re:Announcing the new Rust package manager, Cargo by mcguire on Tuesday March 18, 2014 @01:07PM (#7423236)

"I don't know much about Rust, but AFAIK it's mostly static linking like Go."

Afraid not, at least by default.

[ Parent | on HN ]

Re:Announcing the new Rust package manager, Cargo by azth on Tuesday March 18, 2014 @05:27PM (#7425105)

It is: https://news.ycombinator.com/item?id=7419980

[ Parent | on HN ]

Re:Announcing the new Rust package manager, Cargo by mcguire on Wednesday March 19, 2014 @03:08PM (#7430943)

Weird.

I have one program here using libstd-3e5aeb83-0.9.so, libgreen-83b1c0e5-0.9.so, librustuv-2ba3695a-0.9.so, libcombinations-6b2260d9-1.0.so, and libbisect-441e5ec3-1.0.so (the last two are local libraries). And I have another that doesn't, according to ldd. Both compiled with the same flags.

[ Parent | on HN ]