| Summary: | portage ebuild parameter broken (or bad emerge man page info) | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Jonathan Nall <nall> |
| Component: | Unclassified | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Fixed in cvs. |
this bug is with respect to portage-2.0.42. the emerge man page states the following re: the ebuild parameter: ebuild An ebuild must be, at a minimum, a valid Portage package directory name without a version or cate- tory, such as portage or python. Both categories and version numbers may be used in addition, such as sys-apps/portage or python-2.2.1-r2. emerge ignores a trailing slash so that filename comple- tion can be used. The ebuild may also be an actual filename, such as /usr/portage/app-admin/python/python-2.2.1-r2.ebuild. however, it seems that neither categories nor version numbers may be used. that is: emerge dev-lang/python-2.2.1-r2 does not work. NOTE: this does not affect dependency parameters. ie: emerge =dev-lang/python-2.2.1-r2 works just fine. i don't know if this is a bug in portage or just incorrect documentation.