I'm not 100% sure whether this is due to FEATURES="binpkg-multi-instance" or is a difference in internal code, but recently building binpkgs manually for a catalyst run, I have .tbz2 archives created instead of xpak's. Is the generation code standardised for binpkg creation between 'emerge --buildpkg' and 'ebuild package' or is this something controlled by the 'binpkg-multi-instance' FEATURE option? I believe a simple rename works, but I see elsewhere there could be a missing trailer. Tangentially, I was wondering where potential Zstd archive support may be, but I will likely open a separate bug and link it also to #629538 .
I'd say this is going to be obsolete for gpkg.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=e799003581e49a3ba2aac0d49821f52ed6eda931 commit e799003581e49a3ba2aac0d49821f52ed6eda931 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-12-14 04:57:57 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-12-14 05:03:15 +0000 man/make.conf.5: describe binpkg suffix - BINPKG_FORMAT="xpak" has suffix .tbz2 for any compression type(!) - BINPKG_FORMAT="xpak" and FEATURES="binpkg-multi-instance" (default as of bug #715112) has suffix .xpak. - BINPKG_FORMAT="gpkg" has suffix .gpkg. Bug: https://bugs.gentoo.org/696080 Bug: https://bugs.gentoo.org/715112 Bug: https://bugs.gentoo.org/721070 Bug: https://bugs.gentoo.org/885799 Signed-off-by: Sam James <sam@gentoo.org> NEWS | 3 +++ man/make.conf.5 | 10 +++++++--- 2 files changed, 10 insertions(+), 3 deletions(-)
