On Sat, 2023-07-08 at 18:00 -0400, bill-auger wrote: > that comment in the PKGBUILD is confusing: > > # The prosody-modules repository doesn't have tags that correspond to > > # the prosody releases. So we used the commit right before June 09 > > # to correspond to the prosody release. > > if the upstream does not tag the VCS properly, then where does pkgver='0.12.3' > come from? - the suggestion seems to be that the upstream releases > versioned tarballs - in that case, we should always prefer the tarball release > to VCS - or do they only release binaries? > > in ether case i would ask them to release tarball sources (ideally), or at > least to tag the VCS properly > _______________________________________________ > Dev mailing list > [email protected] > https://lists.parabola.nu/mailman/listinfo/dev
The VCS is for community contributions, and while most of the software there has proper licensing unlike what usually happens to contrib repos, the model is essentially of a rolling release. Hence, the upstream doesn't have proper releases as such and tagging cannot be done. This is why I've resolved to versioning it according to the current prosody version that is available in the repos - as generally the modules target the latest stable version and that is what parabola tracks too. Otherwise this would technically require constantly updating the package which is unfeasable, and in practice most deployments require the admins to manually pull the latest VCS version whenever they've updated the prosody daemon. There are two main issues I can see with this approach, but I don't think they're quite serious: 1) If someone installs a newer version of the modules package than that of the core prosody daemon package, they might have compatibility issues - but that necessarily means that they've intentionally not updated prosody on their system (as this package aims to track the prosody package). 2) There are some modules that would get updates in the VCS repo, but the updates won't reach this package until the prosody package gets updated. For most cases this isn't a big issue though as in practice most sysadmins only update the modules when they update prosody. -- Kind Regards, Wael Karram.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Dev mailing list [email protected] https://lists.parabola.nu/mailman/listinfo/dev
