Summary: | 'dohtml -r ${directory}/' has undocumented behavior | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Arfrever Frehtes Taifersar Arahesis <arfrever.fta> |
Component: | PMS/EAPI | Assignee: | PMS/EAPI <pms> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Arfrever Frehtes Taifersar Arahesis
2012-07-08 06:59:50 UTC
The council has deprecated dohtml in its 20140909 meeting, see bug 520546. :) "doins -r a/b/c/" behaves like "doins -r a/b/c", because it is the same path if "c" is a directory. Especially, the last pathname component is "c" in both cases. This is in line with the pathname resolution as specified in http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_12 and with the behaviour of coreutils (e.g. basename and dirname utilities). I fail to see in what way this would be undocumented. We also shouldn't reuse this bug (which is about dohtml) for an unrelated issue. If doins in Portage behaves differently from what is described in comment #3, I suggest opening a new bug. |