[2023-01-03T00:11:19+0000] <@floppym> sam_: If you run bin/emerge --version directly from portage.git, it outputs X_pY as the version, where X is the latest portage-* tag and Y is the number of commits on the branch since that tag. [2023-01-03T00:11:35+0000] <@floppym> sam_: For portage-9999, it just uses whatever is in setup.py at the time of install. [2023-01-03T00:12:28+0000] <@floppym> Might be possible to add similar code to setup.py for the live ebuild. [2023-01-03T00:13:16+0000] <@floppym> See VERSION in lib/portage/__init__.py. This would let 'emerge --info' show nice output when installed via portage-9999 in the ebuild. When we run it from git, we see: ``` $ bin/emerge --info | head -1 Portage 3.0.44_p39 (python 3.11.2-final-0, default/linux/amd64/17.1/hardened, gcc-13, glibc-2.37, 6.1.12-gentoo-dist-hardened x86_64) ``` Note the "_p39".
This is fixed by the Meson version (thanks Chewi!)
We may still want to switch to e.g. gnulib's git-version-gen, but I'll handle that if we're going to do it.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=858dfd771ac4c6c9315ac5851f4aeeb233fc21d5 commit 858dfd771ac4c6c9315ac5851f4aeeb233fc21d5 Author: Sam James <sam@gentoo.org> AuthorDate: 2023-08-09 02:54:12 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-08-09 02:54:12 +0000 sys-apps/portage: add 3.0.50 Closes: https://bugs.gentoo.org/908971 Closes: https://bugs.gentoo.org/640658 Closes: https://bugs.gentoo.org/894398 Closes: https://bugs.gentoo.org/895908 Closes: https://bugs.gentoo.org/909067 Closes: https://bugs.gentoo.org/909148 Closes: https://bugs.gentoo.org/909853 Closes: https://bugs.gentoo.org/910035 Closes: https://bugs.gentoo.org/910376 Closes: https://bugs.gentoo.org/911594 Closes: https://bugs.gentoo.org/911574 Signed-off-by: Sam James <sam@gentoo.org> sys-apps/portage/Manifest | 1 + sys-apps/portage/portage-3.0.50.ebuild | 229 +++++++++++++++++++++++++++++++++ 2 files changed, 230 insertions(+)