You are not logged in.
I've noticed that the x64 Arch package versioning convention (package.x.y-<pkgver>) has changed to the new "package.x.y-<pkgverX>.<pkgverY>" convention. I'd like to know why is that. Is there a technical reason for that? if not, why was it changed?
Last edited by thePiGrepper (2017-12-08 22:24:33)
Offline
Yes, it's a technical reason:
We needed to rebuild some packages multiple times, because (for one or another reason) built packages turned out to be broken at a time, when they already have been published in testing or community-testing.
The "sub_pkgrel" (as it's called in the build master's scripts) ensures two things: First, pacman will see, that there is a new package and upgrade the old, broken one. Secondly, if someone reports a bug with a package, we know exactly, which package he refers to.
All newly built packages will have the sub_pkgrel - all older packages will stay without, but will be treated as if they had ".0" appended.
Does this mean any difficulty for you? (I guess, you're from a downstream distribution - correct me if I'm wrong)
cheers,
deep42thought
Offline
My system has transitioned from the mainline Arch to Arch32, so I was surprised to see the version convention change. one question though, will this have any implication if/when I try to install a package with AUR? i think not right?
Offline
This should not have implications for aur: A package from aur may depend on a specific version, but it should not depend on pkgrels (I don't even know if this is possible at all).
Offline