Summary: | [Future EAPI] unpack jar files | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Daniel Hancock <dw5_hancock> |
Component: | Core | Assignee: | PMS/EAPI <pms> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | esigra |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 100584, 100588 | ||
Bug Blocks: | 174380 | ||
Attachments: | ebuild.sh.unpack_jar.patch |
Description
Daniel Hancock
2005-08-24 12:58:54 UTC
Created attachment 66789 [details, diff]
ebuild.sh.unpack_jar.patch
Amateurs? Your behaviour/comments on this bug and others imply you to be the amateur frankly- either that or attempting to get a rise out of people. Discontinue that crap when asking others to help if you want people to do what you request. The attitude is a bit much considering your rant is over 4 characters nobody else has yet seen need to request. this may cause regressions in java ebuilds which rely on fallback behavior of portage to simply copy the .jar to $WORKDIR those ebuilds are broken already imo though, so it doesnt matter to me This is requested for 100584, which has been slapped shut. So... Stuart's patch ain't going in. Re-assigning to pms-bugs since this is conceivable for a future EAPI. Is this still an issue? Wouldn't that be a good candidate for unpacker.eclass? This bug was fixed in: http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commitdiff;h=a686e410fd4d20f1d67b1c991936de78379d00c1 +\item[unpack] Unpacks a source archive into the current directory. Must be able to unpack the + following file formats, if the relevant binaries are available: ... + \item zip files (\t{*.zip, *.ZIP, *.jar}) (with \t{unzip} available) looks like PMS includes this in EAPI=0 already \item zip files (\t{*.zip, *.ZIP, *.jar}). Ebuilds must ensure that Info-ZIP Unzip is installed. |