Created attachment 353400 [details] fplll-4.0.4.ebuild example ebuild attached caused by the wildcard
proposal: for d in README* ChangeLog AUTHORS NEWS TODO CHANGES \ THANKS BUGS FAQ CREDITS CHANGELOG ; do if [[ -s "${d}" ]] ; then if [[ "${d}" == *.html ]] ; then dohtml "${d}" else dodoc "${d}" fi fi done
(In reply to Julian Ospald (hasufell) from comment #1) > for d in README* ChangeLog AUTHORS NEWS TODO CHANGES \ > THANKS BUGS FAQ CREDITS CHANGELOG ; do > if [[ -s "${d}" ]] ; then > if [[ "${d}" == *.html ]] ; then > dohtml "${d}" > else > dodoc "${d}" > fi > fi > done TBH, I don't like this. It adds some clutter to the default function, and I wonder how many ebuilds could actually profit from such special treatment of README.html. If we are going to change something, I'd rather drop the wildcard and install plain README only.
(In reply to Ulrich Müller from comment #2) > (In reply to Julian Ospald (hasufell) from comment #1) > > for d in README* ChangeLog AUTHORS NEWS TODO CHANGES \ > > THANKS BUGS FAQ CREDITS CHANGELOG ; do > > if [[ -s "${d}" ]] ; then > > if [[ "${d}" == *.html ]] ; then > > dohtml "${d}" > > else > > dodoc "${d}" > > fi > > fi > > done > > TBH, I don't like this. It adds some clutter to the default function, and I > wonder how many ebuilds could actually profit from such special treatment of > README.html. > > If we are going to change something, I'd rather drop the wildcard and > install plain README only. clutter?
Mainly the dohtml, which I expect to be useful in rare cases only. This isn't appropriate for a default function.
I cannot follow that logic. The default function misbehaves and needs to be fixed.
It's a *default* function, so it is expected that it cannot handle all cases. There's always the possibility to write your own src_install() for the few ebuilds that need it.
(In reply to Ulrich Müller from comment #6) > It's a *default* function, so it is expected that it cannot handle all > cases. There's always the possibility to write your own src_install() for > the few ebuilds that need it. handling more cases by default reduces the need of writing your own functions, so it is an improvement
No need for a function, defining DOCS is enough. Anyway, I suggest that you get consensus in the -dev ML if you want this feature.
Two points: 1. we don't support any kind of explicit excludes. This one feels like implicit exclude, and is inconsistent with this. It's going to be confusing. 2. I feel like html/ fits better big docs with index.html and so on. Creating the directory for single README file is just wrong.
(In reply to Ulrich Müller from comment #8) > Anyway, I suggest that you get consensus in the -dev ML if you want this > feature. AFAICS, no such discussion has taken place. No progress since one year, therefore closing.
