Hi,
following the dub / code.dlang.org policy, I added a version tag to one of my projects: Pegged.
http://code.dlang.org/packages/pegged
The github repo now has a "v0.1.0" tag.
Now, the package was registered by Sönke, not by me. So how do I change the
"dependencies": {
"pegged": "~master"
description in the project installation section to
"dependencies": {
"pegged": "~>0.1.0"
or something equivalent?
Am 29.08.2014 18:24, schrieb Philippe Sigaud:
Hi,
following the dub / code.dlang.org policy, I added a version tag to one of my projects: Pegged.
http://code.dlang.org/packages/pegged
The github repo now has a "v0.1.0" tag.
Now, the package was registered by Sönke, not by me. So how do I change the
"dependencies": { "pegged": "~master"description in the project installation section to
"dependencies": { "pegged": "~>0.1.0"or something equivalent?
The registry automatically picks up new tags after a while (it seems to
have found the 0.1.0 one now), so usually there is nothing more to do.
BTW, if you have a user account on code.dlang.org, I can transfer the
repository ownership to you, so you can see any possible error messages
(just need your username or the e-mail address used for registration).
On Fri, 29 Aug 2014 19:55:46 +0200, Sönke Ludwig wrote:
The registry automatically picks up new tags after a while (it seems to
have found the 0.1.0 one now), so usually there is nothing more to do.
Great!
How does that work? What if I create a v0.1.1 tag, which I don't want being referred to?
BTW, if you have a user account on code.dlang.org, I can transfer the
repository ownership to you, so you can see any possible error messages
(just need your username or the e-mail address used for registration).
Yes, that'd be just as well.
username: philippesigaud
e-mail: philippe.sigaud@gmail.com
Am 29.08.2014 20:37, schrieb Philippe Sigaud:
On Fri, 29 Aug 2014 19:55:46 +0200, Sönke Ludwig wrote:
The registry automatically picks up new tags after a while (it seems to
have found the 0.1.0 one now), so usually there is nothing more to do.Great!
How does that work? What if I create a v0.1.1 tag, which I don't want being referred to?
That's not possible right now, it will always be picked up if it's a
valid SemVer string prefixed by "v". But you could name it just "0.1.1"
or "x0.1.1" to avoid that, or, probably better, name it as a pre-release
version, such as "v0.1.1-alpha.1" or similar. People will be able to
refer to it, but DUB won't automatically use it unless --prerelease is
explicitly specified.
BTW, if you have a user account on code.dlang.org, I can transfer the
repository ownership to you, so you can see any possible error messages
(just need your username or the e-mail address used for registration).Yes, that'd be just as well.
username: philippesigaud
e-mail: philippe.sigaud@gmail.com
Done. Should show up in your "My packages" list now.
On Fri, 29 Aug 2014 20:55:19 +0200, Sönke Ludwig wrote:
How does that work? What if I create a v0.1.1 tag, which I don't want being referred to?
That's not possible right now, it will always be picked up if it's a
valid SemVer string prefixed by "v". But you could name it just "0.1.1"
or "x0.1.1" to avoid that, or, probably better, name it as a pre-release
version, such as "v0.1.1-alpha.1" or similar. People will be able to
refer to it, but DUB won't automatically use it unless--prereleaseis
explicitly specified.
Thanks for your detailed answer. That was stupid of me anyway. If I use a SemVer tag, of course I want people to refer to it.
It's good to know I can use other tags and that DUB won't catch it. I sometimes tag commits in dev branches.
Btw, does DUB scan all branches or only the 'master' one?
Done. Should show up in your "My packages" list now.
Yes, I see it. Thanks a lot for your great work!
Am 29.08.2014 21:14, schrieb Philippe Sigaud:
On Fri, 29 Aug 2014 20:55:19 +0200, Sönke Ludwig wrote:
How does that work? What if I create a v0.1.1 tag, which I don't want being referred to?
That's not possible right now, it will always be picked up if it's a
valid SemVer string prefixed by "v". But you could name it just "0.1.1"
or "x0.1.1" to avoid that, or, probably better, name it as a pre-release
version, such as "v0.1.1-alpha.1" or similar. People will be able to
refer to it, but DUB won't automatically use it unless--prereleaseis
explicitly specified.Thanks for your detailed answer. That was stupid of me anyway. If I use a SemVer tag, of course I want people to refer to it.
It's good to know I can use other tags and that DUB won't catch it. I sometimes tag commits in dev branches.
Btw, does DUB scan all branches or only the 'master' one?
It always scans all branches and all tags (no matter which branch(es)
they are on). Maybe at some point it will be changed to only scan for
tags and not look at branches anymore at all, but that still needs to be
decided.
On 2014-08-29 21:23, Sönke Ludwig wrote:
It always scans all branches and all tags (no matter which branch(es)
they are on). Maybe at some point it will be changed to only scan for
tags and not look at branches anymore at all, but that still needs to be
decided.
There's no such thing as tags on a branch. A tag i just a name for a
specific commit. All tags will be found regardless of which branch the
commit "belongs" to. Unless you can do some tricks to avoid that.
/Jacob Carlborg
Am 30.08.2014 12:10, schrieb Jacob Carlborg:
On 2014-08-29 21:23, Sönke Ludwig wrote:
It always scans all branches and all tags (no matter which branch(es)
they are on). Maybe at some point it will be changed to only scan for
tags and not look at branches anymore at all, but that still needs to be
decided.There's no such thing as tags on a branch. A tag i just a name for a
specific commit. All tags will be found regardless of which branch the
commit "belongs" to. Unless you can do some tricks to avoid that.
To be completely precise, a tag can of course be on one or more
branches, just like a commit itself can (although it doesn't have to).
But there is no direct relationship between the two apart from the
commit graph and both are stored by GIT in separate "lists".
