On Fri, 21 Apr 2017 11:41:44 GMT, Joshua Hodkinson wrote:
On Wed, 19 Apr 2017 22:47:39 GMT, JamesD wrote:
Objective
How to manage a dub package repository?
- Create repository on GitHub [DONE]
- Tag the repository with a version [DONE by creating a release on GitHub]
- Register with the dub package registry https://code.dlang.org/ [DONE]
- From my local PC: dub fetch <mypackage> [DONE]
- Commit a change to GitHub that is picked up by the dub pkg repository [INTERMITTENT]
Questions:
Having problems with the dub package repository updating with my merge on GitHub. It's a simple project with only 1 branch, the master.
- Must I create a new release to update the version tag every time I commit to the master, so that the dub package repository will see this change?
- Is there some alternate method to update the version tag on GitHub, other than create a release?
- I understand it takes some time for the dub pkg repository to update from GitHub. Is the norm 1 hour, 1 day, or longer?
- I triggered a manual update from the dub pkg repository yet I get the following package error:
Version 0.1.2: Package description contains an obsolete "version" field and does not match tag 0.1.2: 0.1.1
- The error above stemmed from me having a (depreciated) version field in my dub.json file.
- I replaced the dub.json with a dub.sdl, removed the depreciated version field, and created a new release.
- I can probably fix by creating yet another release, but I would appreciate some guidance if I'm going astray or not?
I believe you can/should be creating tags with git https://git-scm.com/book/en/v2/Git-Basics-Tagging
and then pushing those up to github.
excellent pointer, thank you!
I've been using GitHub desktop on Windows, but I know how to get to the shell to try your recommendation.
Everything is working fine with dub pkg repository seeing my commits, as long as I create a new release and version. I'm guessing the git command line does the same thing, but I'll check it out.