xorg-x11 has a dependency on app-doc/xorg-docs even when doc useflag is not set I think with USE="-doc" I shouldn't need anything in app-doc It looks to me like app-doc has documentation-generating programs like doxygen, and general interest documentation like linux-from-scratch. Application-specific documentation belongs alongside the app in the portage tree. It would be very bad if app-doc became a catch-all for "application documentation", because it would grow to equal size to the rest of the portage tree, and would make the whole category system useless, as well as not playing well with rsync excludes (how I caught this)
How would it possibly do that? 99% of packages do not have another package designed to be installed separately that is purely docs.
The category is just fine, plus excluding categories from rsync is not really our business, it's your decision and it's not supported in any way, let alone a reason for shuffling with packages.
twisted-docs, cheetah-docs, firebird-docs, smarty-docs, gnome2-user-docs, linux-docs, wxpython-docs, java-sdk-docs, python-docs, portage-manpages, funny-manpages, asr-manpages are all classified according to the program they document. opengl-manpages, xorg-docs, root-docs, php-docs are all in app-docs. It seems this is really inconsistent. Does "app-doc" mean documentation for applications or applications to do documentation? Applications to do documentation seems more in line with app-editors, etc... but maybe doc++, dox, doxygen, NaturalDocs, et. al would better belong in dev-?. What doesn't make any sense at all is for doxygen and xorg-docs to be in the same category. At the very least, xorg-x11 with USE=-doc shouldn't pull in app-doc/xorg-docs.
Consistency is nice, but frankly which category a package is it doesn't matter a lot. xorg-docs provides some necessary man pages with USE="-doc" -- with USE="doc" it provides a whole lot of documentation on the specifications as well.
Done discussing this.
