3 ms·
I think it would be terrible for Rust design/evolution/policy be constrained with that kind of enterprise badness that basically bans crates.io, and crates.io i
by hsivonen 10y ago
I think it would be terrible for Rust design/evolution/policy be constrained with that kind of enterprise badness that basically bans crates.io, and crates.io is an awesomeaspect of the Rust ecosystem.
- pjmlp 10y agoI can tell it is lots of "fun" when you can only use a Maven mirror, with approved jars. To get a jar into that mirror, a request needs to be sent to the legal team describing the license and business case use, after approval the IT team will add the said jar to the mirror. The same applies to version upgrades of already approved jars. This is a typical scenario I had already in a couple of projects.
- adrianN 10y agoI agree that this sucks, but not doing it that way is dangerous for the company because developers might not care enough about license compliance when they include some stuff into their project.
- pjmlp 10y agoI also agree, as I have been through what happens when developers do exactly that and then it gets discovered the worse way.
- wilmoore 10y agoYou willingly subject yourself to this? Why?
- hibbelig 10y agoJust a guess: it pays the rent.
- Manishearth 10y agoIt's not a constraint as much as it is a consideration imo.