As an end user …
I’m just glad and grateful that HaikuWebkit can be updated finally …
1 Like
Haikuwebkit currently has no “-N” appended, isn’t that just a haikuports thing? In any case, the repo contents and the tag changed, so a new version number seems fine. even if the changes (some more included things in a build script) seem miniscule at best
Somehow, it is. It’s the package release indicator, you can use that to make a bump when just a rebuild is necessary or simply when you fixed a typo in the description.
If you had added a -N to the source release, the package would have been named something like haikuwebkit-1.9.28-2-1.hpkg. I’m not sure that it looks better at the end.
It certainly doesn’t look better, but it would convey the fact that it is only a rebuild without changes in the source repository.
But as nephele pointed out, that is not even the case here.
To elaborate a bit, I changed the version so the repo version and the script I use to generate the release are In sync. I would much prefer someone be able to re-generate the tarball from saved instructions rather than someone having to ask me “what’s up with these additional files in the tarball?”
I could also have fixed the script a bit and generate a better tarball, but then next release someone might ask me why it’s not working anymore 