-
Notifications
You must be signed in to change notification settings - Fork 22
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
Towards 1.0 - breaking changes #30
Comments
I'm inclined to just make reregistration not give an error at all, only explain that it's not going to perform a registration. |
On the subject of reregistration. When testing initial package development locally, I frequently want to reregister v0.1.0 until I'm ready to go public. It would help me if there were a way to force registration. |
I'm not going to make it convenient to change anything that has already been entered into the registry; that goes counter to the whole idea of the Julia registries. Of course you can do anything you want with your own registry so make a script which combines a |
Going forward I'd like to make some changes, some of which need to be breaking. This issue is intended to announce what's coming up and giving a chance to discuss it.
To begin with this is what I want to achieve:
DEPOT/registries
is not a git clone. Implemented in Support registering with a temporary git clone and on a specific branch. #47.both for registration of new versions and new packages. The latter requires that exactly one registry is installed besides General. First part implemented by #32, second part by #35. Extended further in #47 to also register a package in the current directory if the active project is not a package.
The necessary breaking changes identified so far are:
git push
the registry changes by default, Push by default #7. This is probably the more useful default anyway and if making the registration changes in a separate clone of the registry, possibly in a temporary location, manual pushing will be quite inconvenient. Implemented in Push registry after registrations by default. #36.registry
argument toregister
from positional to keyword. With the option to register based on the current project it would no longer be obvious if a single argument specifies a package or a registry. Implemented in Switch registry argument to register from positional to keyword. #35.isinteractive
.Further incoming breaking changes will be added to this list.
The text was updated successfully, but these errors were encountered: