Open vulpivia opened 4 years ago
nedpals
commented
4 years ago Thats the purpose of tags in git. vpkg does indicate both the version indicated in the vpkg.json/v.mod and the commit hash at the end of installation but I have yet to add a mechanism in specifying the version of the packages through git tags.
vulpivia
commented
4 years ago vpkg does indicate both the version indicated in the vpkg.json/v.mod and the commit hash at the end of installation
What does indicate mean in that context? That it's only used to show the user which version was installed?
When versions are specified using git tags, will the version number become obsolete? I might look into how we can use git tags if I find the time in the next few days.
nedpals
commented
4 years ago What does indicate mean in that context? That it's only used to show the user which version was installed?
Yes. But I also forgot to mention that both the commit hash and version listed at the package manifest is also recorded to the lockfile.
When versions are specified using git tags, will the version number become obsolete? I might look into how we can use git tags if I find the time in the next few days.
It won't. Git tags aren't the best way to do versioning and version numbers indicated at the manifest will remain for double-checking.
How is versioning handled? If I understood the code right, the "update" command always updates to the most current commit in a repository.
If that's the case, wouldn't it make more sense to get the repository at the commit in which the version number has been changed or something like that? A new version would then be created when the version number in vpkg.json changes.