Dave Reisner <d...@falconindy.com> on Sat, 2017/07/01 13:22: > Hey all, > > This should be pretty much a no-brainer, but wanted to be sure I wasn't > missing anything. Systemd upstream publishes a "systemd-stable" repo [1] > which branches at each tag and cherry-picks backports. I'd like to > switch our systemd package to this repo to avoid some of the duplication > of work that Jan, Christian and myself have done in the past. The repo > sees a bunch more activity than what our own backporting strategy has > been, and I see that as a positive. > > One potentially bikeshed-worthy question is versioning. Do we count > commits and modify the pkgver every time we build from the repo, e.g. > 233.23-1 (meaning pkgrel=1 of a v233 build containing 23 backports), or > do we simply keep the base pkgver true to upstream and increment pkgrel > every time we release, e.g. 233-5 (meaning pkgrel=5 of some build of the > v233 stable branch). > > [1] https://github.com/systemd/systemd-stable
I like the versioning to indicate what the package contains... So voting for the inclusion of commit count. The only downside will be that people will flag the package out-of-date for every new commit in the stable branch. :-p -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
pgp96SZMMiRNL.pgp
Description: OpenPGP digital signature