Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 425214 - 'dohtml -r ${directory}/' has undocumented behavior
Summary: 'dohtml -r ${directory}/' has undocumented behavior
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: PMS/EAPI (show other bugs)
Hardware: All All
: Normal normal (vote)
Assignee: PMS/EAPI
Depends on:
Reported: 2012-07-08 06:59 UTC by Arfrever Frehtes Taifersar Arahesis
Modified: 2014-09-13 13:24 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Arfrever Frehtes Taifersar Arahesis 2012-07-08 06:59:50 UTC
'dohtml -r ${directory}' installs e.g. /usr/share/doc/${PF}/html/${directory}/${file}.

With Portage, 'dohtml -r ${directory}/' installs e.g. /usr/share/doc/${PF}/html/${file}, so it behaves similarly to
'dohtml -r ${directory}/*', but it also installs files/directories whose names start with a dot (except names equal to "." and "..").

Currently at least 138 ebuilds in gentoo-x86 rely on this behavior.

If this behavior is intentional, then it should be documented.
Comment 1 Ulrich Müller gentoo-dev 2014-09-13 11:20:17 UTC
The council has deprecated dohtml in its 20140909 meeting, see bug 520546.
Comment 2 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2014-09-13 12:41:46 UTC
Comment 3 Ulrich Müller gentoo-dev 2014-09-13 13:11:39 UTC
"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 and with the behaviour of coreutils (e.g. basename and dirname utilities).

I fail to see in what way this would be undocumented.
Comment 4 Ulrich Müller gentoo-dev 2014-09-13 13:24:27 UTC
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.