| 1 |
On Mon, 2018-10-01 at 19:23 +0200, Andreas Sturmlechner wrote: |
| 2 |
> On Montag, 1. Oktober 2018 17:48:16 CEST Michał Górny wrote: |
| 3 |
> > On Mon, 2018-10-01 at 08:19 -0700, Zac Medico wrote: |
| 4 |
> > > /usr/share/doc level directories |
| 5 |
> > > ================================ |
| 6 |
> > > /usr/share/doc/${PF} |
| 7 |
> > > |
| 8 |
> > > The first bug report [2] is for qt-core, which installs documentation |
| 9 |
> > > into /usr/share/doc/${PN}-${PV} instead of /usr/share/doc/${PF} (${PF} |
| 10 |
> > > includes ebuild revision such as -r1, -r2, and so on). |
| 11 |
> > |
| 12 |
> > No, it doesn't. There's no /usr/share/doc/qtcore-5.11.1 on my system. |
| 13 |
> |
| 14 |
> This is coming from dev-qt/qt-docs. |
| 15 |
|
| 16 |
Nope, still not /usr/share/doc/qt*core*-... |
| 17 |
|
| 18 |
> It is a problem because any other package |
| 19 |
> building QCH API docs with cross-references to Qt API needs to install below |
| 20 |
> this path, and will generate the same QA warning (currently kde-frameworks/* |
| 21 |
> does this). |
| 22 |
|
| 23 |
Yes. That is why I believe that hardcoding the exception in every |
| 24 |
package is simply wrong. Wouldn't it be cleaner to account for the path |
| 25 |
in the QA check? |
| 26 |
|
| 27 |
-- |
| 28 |
Best regards, |
| 29 |
Michał Górny |
Archives