New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename the repos #232
Comments
I also find this confusing, and keep forgetting the crate name for |
Having the crate name without -rs suffix is totally normal, i.e. cgmath crate used to be hosted in "cgmath-rs" repo, which got renamed upon moving to "rustgb" org. There are still cgmath-rs forks found on github. Renaming I do admit that the state of things is not ideal today, and it's not obvious from the first sight where things are. I suggest we delay the discussion to the time where Gecko integration is happening, and keep the names unchanged till then. It might be possible, for example, that the |
This is an anti-pattern imho, and unfortunately keeps being perpetuated in rust crates. Just because people do it, doesn't mean they should; another example of this is Anyway, I'm risking derailing this on "normal" naming schemes, but you don't have to follow what is arguably "normal" or not, and I just think its clearer if the repo is named the same as the crate, that way there's zero ambiguity. A similar pain point in ocaml: where the library name on opam (the package manager) isn't the same as the module name used in code, and it's just... annoying. Anyway, just my two-cents. |
If gecko integration is still a long way off, I think we should change the I agree that keeping the |
Yea I agree with @rukai, at very least it makes sense to figure out proper repo for wgpu-native |
Repositories with multiple crates are the norm too. Integration with Gecko should have started a while ago. It's already delayed past the schedule. It's not a long way off. |
Sure, a repo can have more than one crate. However, when the So what shouldn't happen is that there's a repo named Here's some possible paths to fixing the situation and making it much more approachable to new users:
|
@Lokathor this is reasonable. Note that we used to have everything in a single repo, but recently separated them, because some of the things are meant to be synchronized from Gecko. One of the possible outcomes is: wgpu-remote gets completely moved to Gecko, community isn't interested in using it, so we don't sync it back to Github. Therefore, Github's project can be safely renamed to |
Inspired by gfx-rs/wgpu#232
Now that |
I think there is still a bit of a desire (voiced by @grovesNL previously) to rename this repo to |
It looks like waiting paid off! |
232: Update to latest wgpu, duplicate RequestAdapterOptions r=kvark a=kvark Co-authored-by: Dzmitry Malyshau <kvarkus@gmail.com>
Post hal move, everything is in this one repo, so closing. |
Have single place where advancing to next line
After a discussion in the rust community discord I was reminded how confusing the wgpu naming is.
There are two main wgpu crates that people care about:
wgpu
andwgpu-native
.Currently they belong to these repos:
I propose we rename like this:
If we are open to changing crate names, then we could do this:
The text was updated successfully, but these errors were encountered: