| Summary: | portage-2.2_rc1 does not handle spaces in files with fetch restriction | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Daniel Black (RETIRED) <dragonheart> |
| Component: | Core | Assignee: | PMS/EAPI <pms> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | pacho |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 174380 | ||
| Attachments: | truecrypt-6.0.ebuild | ||
Created attachment 159866 [details]
truecrypt-6.0.ebuild
spaces are used as separators in metadata variables. (In reply to comment #2) > spaces are used as separators in metadata variables. Marius, with due respect, and I do respect you a lot, this sounds like a excuse. It sounds like an internal design consideration rather than a specification problem. Well, one possible solution would be to add single quotes, like this:
SRC_URI="'TrueCrypt ${PV} Source.tar.gz'"
(In reply to comment #4) > Well, one possible solution would be to add single quotes, like this: > > SRC_URI="'TrueCrypt ${PV} Source.tar.gz'" And what will you do for filenames containing single quotes then? ;-) <http://www.faqs.org/docs/artu/ch05s02.html> is worth reading... Does anyone want to do this anymore? It looks like the idea is hard to implement, and TrueCrypt is no more :). I think we should WONTFIX it. I believe that this is obsolete: Escape mechanisms for URIs exist, and in addition we have SRC_URI arrows that allow saving the distfile under a reasonable name. |
SRC_URI="TrueCrypt ${PV} Source.tar.gz" stat("/usr/portage/distfiles/Source.tar.gz", 0x7fff38f7bdc0) = -1 ENOENT (No such file or directory