Summary: | portage unpack() function uses only file extension | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | jieryn <jieryn> |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | mmokrejs |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info |
Description
jieryn
2007-04-17 14:09:07 UTC
Created attachment 116508 [details]
emerge --info
How about using something similar to this in the ebuild? src_unpack() { myA=${A%.*}.tar mv ${DISTDIR}/${A} ${DISTDIR}/${myA} unpack ${myA} } This would cause refetch of the .pdb every time. Then use cp, I was just pointing to the fact that you can manipulate the file before unpack. Yep, that is the work around I'm using now. I beleive that unpack can, and should, be smarter about prematurely bailing out of an unpack operation. Running `file` on the parameter would quickly show that we're dealing with a GNU archive and are eligible for processing from unpack. i dont see much value in the over head needed in order to properly detect a file by ignoring its suffix ... just symlink it: ln -s ${DISTDIR}/${A} ${A}.tar unpack ./${A}.tar *** Bug 210878 has been marked as a duplicate of this bug. *** |