1.1

В Чтв, 17/07/2008 в 04:51 +0200, Marius Mauch пишет: 
> At dev.gentoo.org/~genone/unpack.eclass is the draft for an eclass
> to implement this feature. 

Marius, although it's possible to do this things in eclass why is eclass
better? As I see portage's unpack() already has extension <-> "program
to unpack" relation. Basically unpack() in ebuild.sh has the following
code:

unpack() {
[snip]
        case "${x##*.}" in
            tar)
                tar xof "${srcdir}${x}" ${tar_opts} || die "$myfail"
                ;;
            tgz)
                tar xozf "${srcdir}${x}" ${tar_opts} || die "$myfail"
[snip and so on...]

This means that every ebuild which uses 'unpack ${A}' should have in
DEPEND a program which is selected by filename extension of sources. So
as I understood your initial suggestion was to make this happen
automatically. And this is very logical as makes ebuilds cleaner and
more terse. So why did you changed your mind and try to write another
eclass (which then should sit in the tree forever), to create duplicate
unpack function instead of just making step you suggested initially? Is
there any intension to remove unpack logic from package manager? And if
yes, why?

-- 
Peter.