I work at a company where our ITS manages “very strictly” installs on our Linux systems through managers like pip, gem installs, apt-get, etc… For example, if I want to install the package on my linux box I must submit a ticket to ITS for this to happen. We have a dedicated server internal to our company network that contains various “approved” packages mirror’d over from their outside counterpart. When ITS gets the ticket then they perform the install. Therefore, my privileges are tightly controlled and having sudo is simply not an option unless it’s a special case.
What implications will this have w/ Rust’s manager cargo. Getting Rust installed I believe is straight forward. It’s my concern that every time I need a new crate, update a crate, run a cargo build with dependencies listed in my cargo.toml, switch/update releases that I will experience server road blocks and issues. However, I’m quite new to this so I would appreciate some advice on what issues I would run into along with any helpful advice I could pitch to our ITS team in working around this.