Summary: | /usr/lib/portage/bin/* doesn't handle files with spaces in the names | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Sandy McArthur <Sandy> |
Component: | Unclassified | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | drobbins, jnelson, vapier |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sandy McArthur
2002-04-10 22:48:50 UTC
OK, we should fix this -- but -- our policy is not to install files with spaces in their names. Do any ebuilds have such files? Not that I know of. I was trying to install a helper file for VMware that added menu items to kde. The file created be kmenuedit (or whatever it's called) gave it a space in the name and I didn't think to rename it. My workaround was to rename it without the space. perhaps Bug 1957 is related to this ? the emerge fails because of spaces in a library configure option Despite the policy of "no files with spaces in them" (which I don't agree with, but won't argue here), for safety' sake it's not a bad idea to robustify the scripts. If the scripts WARN that a file has spaces in it seems like a good middle ground to me. Additionally, while we're on the topic, I've noticed a few shortcomings with the other scripts (dodoc doesn't recurse, etc...). If I may suggest, a discussion on -dev for general script improvement and/or replacement might not be a bad idea. Bash file globs being used to pass files might cause problems as "detecting" spaces is a non-trivial exercise. Using $* and $@ would be one of the major problems as it gets/gives a _space delimited_ list of arguments to for loops and other scripts... Thereby failing anything looking for spaces... I think the palm emulator is one that includes files with spaces. * app-emulation/pose [ Masked ] <--- That's it. in cvs |