On 10/22/18 10:16 AM, Tinu Weber wrote: >> […] More generally, the pkgrel system allowed by the makepkg >> spec doesn't acknowledge the use case of infinitely cascading derivatives. > > That makes me sad, but I'll accept that as an anwer. > > How about pacman/libalpm/vercmp? Can I rely on them treating multiply > dotted pkgrels as expected, or have I entered "expect your stuff to > break one day" territory?
We officially don't allow it, but our spec for what is allowed is "does makepkg lint it as an error". pacman/libalpm is extremely liberal about what it accepts, the current limits are, more or less, "it cannot have newlines, NULL bytes, or a /". pkgver also cannot have "-". Andrew Gregory documents these practical limits here: https://wiki.archlinux.org/index.php/User:Apg#pacman_LIMITS The first two are because of the .PKGINFO line-based format. The last is only because if you do, the pacman "local" database, which is just a directory "${pkgname}-${full_epoch_pkgver_pkgrel}" containing a file called "desc". > I guess for the mortals among us, the best/cleanest way is to bump the > pkgVER (as pointed out by LoneVVolf [2]), and stop attributing any sort > of semantic meaning (upstream/downstream) to the pkgrel? Um, yeah, just noticed your email. :) -- Eli Schwartz Bug Wrangler and Trusted User
signature.asc
Description: OpenPGP digital signature
