Hi, in ebuild.sh: [..] case "${x##*.}" in [..] bz2) if [ "${y}" == "tar" ]; then [..] It should read "bz2|bz)" to also include tar.bz files. The offending line is 387 (portage-2.1_pre9-r1)
bz is invalid imho
I get 212.000 on google for tar.bz Compared to the 6.650.000 tar.bz2 results that makes 3.19%, seems to be widely used. But, anyway, I would like to use it in real-world ebuilds like: http://genstef.homelinux.org/local/kde-misc/kbfx/kbfx-0.4.9.1.ebuild Please add this simple fix, it harms no one.
just because people do it doesnt make it correct :P
File endings as such are an offensive concept (handy though, I'll admit that), but we got to live with what we get ;) On the topic: Looking at http://www.gentoo.org/cgi-bin/viewcvs.cgi/*checkout*/sys-apps/portage/ChangeLog apparently the fix has already been added to Portage 2.1_pre9-r2 though I can't confirm that from my local tree, that sync a few minutes ago didn't grab pre9 yet :( Whether using .tar.bz is correct or not is IMO not important, people DO use it, and I for one can't think of anything that could have this ending other than a bzip2 archive. So I think the patch should stay.
worksforme :) now we just need to get it into the stable portage so that ebuilds can start using it.
(In reply to comment #5) > worksforme :) > > now we just need to get it into the stable portage so that ebuilds can start > using it. with appropriate dep of course...
Released in 2.1_pre9-r2.
