Hi! On 19/11/12 04:42, Dmitry Shachnev wrote: > Hi all, > > This year, we have received two requests to move some files that are currently > shipped in a -doc-html package to another package: > > - https://bugs.debian.org/922707 requests moving the .tags file to -dev. > - https://bugs.debian.org/933597 requests moving the examples-manifest.xml > file and associated images to -examples. > > These bugs are really not specific to qtbase or qt3d, so we should consider > them as affecting all Qt submodule packages. > > The problem > =========== > > TL;DR: We can only ship these files in an Architecture: all package. > > All files that are currently shipped in -doc or -doc-html are generated by > qdoc, which is built from qttools-opensource-src package. As that package > build-depends on qtwebkit, all Qt source packages up to qtwebkit [1] can *not* > build-depend on qdoc-qt5 when building architecture-dependent packages, as > that would create a B-D loop. So qdoc-qt5 can be only in Build-Depends-Indep. > As a consequence, files generated by qdoc can be only in Architecture: all > packages. > > [1]: qtbase, qtdeclarative, qtwebsockets, qtwebchannel, qtsensors, qtlocation > > The questions > ============= > > 1) Should we create new Architecture: all packages (like qt*-doc-dev), to > contain the .tags and examples-manifest.xml files? > > 2) If yes, should it contain both these files or only one of them? Also > should we do it for all submodules, or only for those 6 modules listed > above? > > 3) If no, should we make qt*-dev or qt*-examples recommend qt*-doc-html? > > Note that if the answer is ‘yes’, then we would need to do from 6 to ~30 > uploads to NEW. (This is why I lean towards ‘no’.)
This is my personal opinion, but feel free to implement whatever you see most fit, you are the one doing the job :-) My first approach to this would be: - Creating qt*-dev-doc shipping only the .tags, and just one -dev-doc per submodule. Gotcha in this: if this creates a link in the doc, it should also create a strict dependency in the right -doc package... :S - Make qt*-examples recommend (or even depend upon) qt*-doc-html. If you are trying to test examples you are probably trying to read the related doc too. Of course this would be my first approach, it can be changed upon discussion :-) -- https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-talk
