Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=521909
--- Comment #25 from Michael Schwendt mschwendt@gmail.com 2009-10-02 06:03:05 EDT ---
So, I think we must threat it as "documentation in -devel OR -doc"
There is one unwritten guideline above all others. It's called "consider common sense".
If a -devel package included a couple of "man 3" pages for its API headers and also at least one large PDF file or a huge HTML tree, would you move _all_ %doc files into a separate -doc package? No. Nothing in the guidelines says you must decide between either -devel OR -doc. You are free to move the large files into -doc and keep other documentation files in -devel. It's the obvious solution. And convenient, too. Just as you're free to put further non-development oriented documentation files into other sub-packages.
The original idea to create a -examples package for only six tiny source files was a weird and unpractical idea, and I think now you just don't want to let loose. That's why you show resistance. ;)
Please run command: $ repoquery '*-doc' --requires and you can see ho many -doc subpackages have dependencies.
So what? --v
Off course some of that is errors,
Exactly. :-) Don't treat them as good examples.