app-emulation/lxd-2.4.1 is out. Ebuild attached is verbatim copy of latest lxd-2.2.ebuild in portage, using the repackaging script: https://dev.gentoo.org/~stasibear/lxd_repackage.py. Tested to emerge OK with script generated tarball (Gentoo devs will probably prefer to use maintainer version, so not attaching), and version-specfic renames under files/: lxd-2.2.confd lxd-2.2-dont-go-get.patch lxd-2.2.initd Copy to: lxd-2.4.1.confd lxd-2.4.1-dont-go-get.patch lxd-2.4.1.initd Can this be streamlined to drop the version specifier? The versioned files are identical. Reproducible: Always
Created attachment 449488 [details] lxd-2.4.1.ebuild Verbatim rename of lxd-2.2.ebuild, per tarball repackaging script.
It would be time-consuming to backfill, but recent releases since portage latest lxd-2.2 are: 2.3 2.4 2.0.5 2.4.1
Thanks for doing that. I actually pushed 2.4.1 to git last night, maybe while you were doing all this work :) 2.3 added a lot of kernel config checks to support the new "lxc network ..." commands. Regarding the backfill versions, 2.4 had a version error. The 2.0.x releases are meant to be a stable line off of 2.0.0, but I've skipped them since nothing is marked stable in our tree yet. Regarding the version prefixes under ${FILES}, the files are identical _now_ but they weren't always and may not always be (the Makefile patch will definitely shift again). Have you considered becoming a dev?
