So, here's the question for the list. For the cygwin-specific README in a X-related package, where should it go?
/usr/share/doc/Cygwin/ like "normal" packages? /usr/X11/doc/Cygwin/ ? /usr/X11/share/doc/Cygwin/ ?
I lean toward /usr/X11/doc/Cygwin/ just in the interests of keeping all things X-related under /usr/X11R6/...
Subject to resolution of that issue, and slight reworking of the source package to conform with method2 (basically, just adapt the generic-build-script), this looks good.
The problem I see with even having /usr/X11R6/doc/Cygwin and /usr/X11R6/share/doc/Cygwin/ is that we will continue to have discussions about whether to classify a package and/or its readme as an XFree86 or non-XFree86 package.
Perhaps we should entertain the idea of dropping /usr/X11R6/doc/Cygwin and /usr/X11R6/share/doc/Cygwin in favor of /usr/share/doc/Cygwin?
Then we wouldn't have to ponder about whether linking to/depending on/uses X means that the docs have to go in one place or another.
How does that sound?
Maybe it is also time that we clarify what goes in the XFree86 category and what goes elsewhere. I always feel like I have sort of a way to sneak packages in "under the radar" in my XFree86 category... but it doesn't feel right for me to do this. I should be having my packages reviewed like others do (even if I post them myself). It would thus make sense to clarify what should go in XFree86, what I can post without comment, and where everything else should go as well as the fact that it must be reviewed by other developers.
Harold
