You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there is no easy way when using rustpkg to write:
extern mod foo = "github.com/mozilla/whatever";
and concurrently be developing the whatever package, with local patches that aren't in the github repo. You can make local changes, but rustpkg will overwrite them (although you shouldn't be able to, as per #6480). If you instead check out the sources for whatever into a different directory and work on the copy in that directory, you have to change the extern mod directive and, for the benefit of anyone else using your package, bundle the sources for whatever as a submodule. This is not ideal. I'm not sure how to reconcile wanting to name packages by their URLs with wanting to make local changes to them.
Currently, there is no easy way when using rustpkg to write:
extern mod foo = "github.com/mozilla/whatever";
and concurrently be developing the
whatever
package, with local patches that aren't in the github repo. You can make local changes, but rustpkg will overwrite them (although you shouldn't be able to, as per #6480). If you instead check out the sources forwhatever
into a different directory and work on the copy in that directory, you have to change theextern mod
directive and, for the benefit of anyone else using your package, bundle the sources forwhatever
as a submodule. This is not ideal. I'm not sure how to reconcile wanting to name packages by their URLs with wanting to make local changes to them./cc @metajack since we talked about this before.
The text was updated successfully, but these errors were encountered: