Peter Memishian wrote: [snip] > First, documentation is generally not subject to the same sort of rules. > You'll note that findunref already contains a blanket exception for text > files and READMEs. Second, if the source file can reasonably be argued to > have value on Solaris, then it's fine. However, a directory filled with > (e.g.) Windows NT specific files would be hard to argue for.
The only windows files in the tree are 1. usr/src/lib/libpp/common/probe.win32 2. include/ast_windows.h [1} can likely go away but [2] is an include file which is referenced even on Unix/Linux and therefore we can't remove it easily. > > ... but maybe I am worrying too much... the "findunref" list > > lists "perl" and that may be a good precedent for ksh93... or not ? > > As I mentioned in an earlier email, we generally grant exceptions for > parts of the source tree that are kept in-sync with an upstream source. > But the exception should not be used to stockpile support for non-Solaris > platforms provided that the files could be automatically pruned from the > upstream source without too much effort. See above... AFAIK that are the only files which could be removed. There is little "extra" stuff in the tree (I only checked Win32, MacOS and Linux) ... ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
