| Summary: | sys-apps/portage-2.1.11.38 spaces in the patch filenames | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Andrey Ovcharov <sudormrfhalt> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | pinkbyte, sudormrfhalt |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
This patch fixes the manifest parser to handle spaces in names: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=bdc4b8b09a249451bc471f1a2f03963559a9fb3a In addition, we'll have to add a metadata/layout.conf extension that allows specification of allowed file name characters, as mentioned in bug #411127, comment #7. |
Current sys-apps/portage-2.1.11.38 not support patch file names with spaces. Reproducible: Always Steps to Reproduce: 1. Create any new ebuild or use any existing… In the files/ add a patch containing a space in its name. 2. ebuild <name>.ebuild digest 3. ebuild <name>.ebuild compile Actual Results: ebuild <name>.ebuild compile (cat) !!! A file is not listed in the Manifest: '/usr/local/portage/<name>/<name>/files/<name contains a space>.patch' Expected Results: Manifest with <name contains a space>.patch The current solution: Add thin-manifests = true to metadata/layout.conf > cat /usr/local/portage/metadata/layout.conf thin-manifests = true sign-manifests = false profile-formats = portage-2 cache-formats = md5-dict And take care yourself on handling filenames containing spaces.