You can modify the branch on your metadata fork and remove some of the tag
files. Usually Pkg.publish is used after just one or two local Pkg.tag's.
How can I specify which tags are registered? I think the default commands
I used (Pkg.tag,register, and publish) ended up trying to register all
existing tags in metadata.
On Thu, Sep 8, 2016, 18:47 Tony Kelman wrote:
> git tags that don't get registered in metadata should be fine. What were
>
git tags that don't get registered in metadata should be fine. What were you
seeing happen?
Can tags be used for anything other than versioning in a Package? I was
registering a package with non-version tags marking some important
development points (e.g. a "naacl2016" tag) and the package manager was not
happy about it. If no tags are allowed other than the vX.Y.Z tags, is the
comm
On Thu, Oct 1, 2015 at 6:58 AM, Bill Hart
wrote:
> Just to clarify, "New package version tags must support at least Julia
> version 0.3" means that not supporting 0.3 is ok, i.e. just supporting 0.4
> and up is ok?
>
> And that would be 0.4 if it's 0.4 release and up and 0.4- if it is 0.4
> prere
Just to clarify, "New package version tags must support at least Julia
version 0.3" means that not supporting 0.3 is ok, i.e. just supporting 0.4
and up is ok?
And that would be 0.4 if it's 0.4 release and up and 0.4- if it is 0.4
prereleases and up (the only meaningful thing for 0.4 at this po
