Summary: | [Future EAPI] unpack should match extensions case-insensitively | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | David Leverton <levertond> |
Component: | PMS/EAPI | Assignee: | PMS/EAPI <pms> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | esigra |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=476738 | ||
Whiteboard: | in-eapi-6 | ||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 174380 |
Description
David Leverton
2013-07-13 17:54:06 UTC
Portage does this already: for x in "$@"; do __vecho ">>> Unpacking ${x} to ${PWD}" suffix=${x##*.} suffix=$(LC_ALL=C tr "[:upper:]" "[:lower:]" <<< "${suffix}") # [...] case "${suffix}" in Unfortunately, Portage added that without EAPI control, and pretty late on. We're already hitting issues in the tree. (In reply to Ciaran McCreesh from comment #2) > Unfortunately, Portage added that without EAPI control, and pretty late on. > We're already hitting issues in the tree. Yeah, late in 2012: <http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;f=bin/phase-helpers.sh;h=3dea53c2be83088d05c82a0c3dbbe7e6e1a6edea> @Portage team: Could this be reverted please? We can do it properly for EAPI 6. (In reply to Ciaran McCreesh from comment #2) > We're already hitting issues in the tree. Are we? I've scanned the tree for uppercase suffixes in SRC_URI, and all I can find are .Z (which is a supported extension, according to PMS) and a few .ZIP which are all properly mapped to .zip by -> arrows. So the Portage commit could still be reverted without negative impact on users. |