Portage currently supports lzma files. These are known as being deprecated by the new xz file format. It has some important features like magic bytes and integrity check. The old automake dist-lzma method will be replaced by dist-xz (which is available at the moment in the development version). The file format is marked stable since v4.42.2alpha-286-g982da7e of app-arch/lzma-utils (and was stable since v4.42.2alpha-217-g1880a39 which was commited 2008-11-19). Just for my own sake: An ebuild which uses .xz or .lzma has to add app-arch/lzma-utils to it's own build dependencies? Reproducible: Always Steps to Reproduce:
Created attachment 180066 [details, diff] add support for xz format to ebuild.sh
BTW, we've got bug 249059 for an "lzip" entension. I guess it's a different format though. (In reply to comment #0) > Just for my own sake: An ebuild which uses .xz or .lzma has to add > app-arch/lzma-utils to it's own build dependencies? That's right. The ebuild will also have to specify a newer EAPI value which will exist in the future.
Hm, lzip seems to be something completely different (never heard of it before) and the only persons which work together on the lzma sdk are the guys from lzma-utils (the specification came from Igor Pavlov aka the creator of lzma/7zip and Lasse Collin). This format is also supposed to be integrated in 7zip - dunno if something like this is planned for lzip. This doesn't mean that I am against lzip, but that these are two different and incompatible projects - which makes me a little bit sad.
slack has already move to xz, Gentoo is getting further behind.
Gentoo has some kind of xz support since a long time. Problem is that it needs EAPI=>3 (not available yet) and an unmasked version of xz-utils (not available either). But the support is already available in ebuild.sh and is only waiting for the other two.
Just as an update. xz-utils is unmasked, but not yet masked as stable. Portage has still no support for EAPI-3 in 2.2rc38
Any chances to see xz in portage soon? The bug is almost year old an we seem to be far behind other distros which use xz extensively.
You can already use xz archives in ebuilds, but you have to use the src_unpack() function to manually unpack them. Watch bug #273620 if you want to track EAPI 3 implementation progress for sys-apps/portage.
Moved to EAPI 3 by today's council decision.
