From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] *.tar.lzma is not mentioned
Date: Mon, 29 Jun 2009 19:09:41 +0100 [thread overview]
Message-ID: <20090629190941.5bacc64a@snowcone> (raw)
In-Reply-To: <19014.36909.253256.761452@a1ihome1.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
On Sat, 27 Jun 2009 23:33:33 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:
> PMS doesn't mention lzma-compressed tar files, but Portage (and also
> Paludis, as far as I can see) can unpack them.
>
> And I think calling simple *.lzma and *.xz files "archives" is
> misleading. They are just single compressed files like *.gz or *.bz2.
> Patch is attached.
Applied, thanks (I tweaked the indenting slightly).
> We could also think about reordering the list of extensions. Currently
> it's not very systematic.
Right. I think the order's how things used to be in Portage back when
we made the list. It'd probably look nicer as a table, something like:
Extension EAPIs Must have installed
1 2 3
.tar.gz y y y GNU tar, GNU gzip
.tar.lzma y LZMA Utils
That's an 'easy' exercise for someone who feels like being helpful...
Incidentally, one of the things I was hoping to get in for EAPI 4 was a
fix for the arbitrary and weird dependencies required for unpacking. I
think we briefly discussed doing something like making the package
manager have 'magic' packages, so you'd do:
DEPEND="package-manager-magic/unpack-zip"
to tell the package manager to depend upon whatever it really uses to
unzip things. I don't recall whether this was feasible from a Portage
perspective though.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-06-29 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 21:33 [gentoo-pms] *.tar.lzma is not mentioned Ulrich Mueller
2009-06-29 18:09 ` Ciaran McCreesh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090629190941.5bacc64a@snowcone \
--to=ciaran.mccreesh@googlemail.com \
--cc=gentoo-pms@lists.gentoo.org \
--cc=ulm@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox