3 ms·
which forces people to pay to register a domain just to publish packages...
by brickteacup 3y ago
which forces people to pay to register a domain just to publish packages...
- Ygg2 3y agoI don't think that's necessary, since cargo and source repo is tightly linked, just make that source repo supports returning user name or org name. I don't see a reason you couldn't use exisiting org/username from Github as namespace, can they squat on it? Not unless they steal it, in which case, Github should be notified.
- steveklabnik 3y agoWhat happens when crates are transferred? Everyone's build breaks.
- Ygg2 3y agoWhat do you mean by transferred? Like you have Ygg2/stuff and want it to be replaced by Org/stuff? In that case just yank all versions on Ygg2/stuff, and the any change update from then on references Org/stuff.
- steveklabnik 3y agoYes. For example, the semver package has lived in these places: * rust-lang/semver * steveklabnik/sevmer * dtolnay/semver That everyone didn't need to do "yank everything, change all cargo.tomls" is a huge advantage of not being tied to this.
- Ygg2 3y agoWell change all future `cargo.toml`s. If you want a more complex solution, then you would need a more complex index of ownership for cargo. E.g. alias or transfer ownership. It could be as simple as displaying "This crate is deprecated use org/crate instead". Or as complex as what crate is no longer valid. One needs to know what exactly are cargo namespace requirements? > Yes. For example, the semver package has lived in these places: Sure, and squatters squatted over many crate name extorting bribes to release them.
- MrBuddyCasino 3y agoI think Github repos work too.