On Sun, 23 Apr 2017 13:35:19 GMT, Sönke Ludwig wrote:
On Wed, 19 Apr 2017 22:47:39 GMT, JamesD wrote:
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?
It's technically possible to depend on a particular branch of a package instead of on a version range (e.g. "~master"), but the (strongly) recommended working scheme is to use versions, which indeed requires adding a new version tag for every new set of visible changes.
I understand it takes some time for the dub pkg repository to update from GitHub. Is the norm 1 hour, 1 day, or longer?
The usual time should be about half an hour. If it takes significantly longer that indicates a problem with either the registry server, or with the new version tag (some error condition). Having e-mail notifications for the latter case would be nice, but is not implemented at the moment.
Thank you - All is working with a new version each time.
The update period is as you stated, and is reasonable.
The dub pkg "manage app" page shows how many are being updated before mine.
Now, if I could get my updates right the first time ... he he.