Peter Memishian wrote: [snip] > * READMEs and other textfiles that aid in understanding the source. > (Exceptions for these are automatically granted, provided the files > end in ".txt".)
What about text files like manual pages ? Currently we ship the _original_ ksh93 manual page to have this part of the documentation exactly 1:1 in sync with the code (while the official Solaris ksh93 manual page is a derived version with various changes and usually laggs behind the actual status of the code). Does this fall under the same category as the "text files" waiver or is a seperate explanation needed ? > * Source that's used during "specialized" builds, such as CRYPT_SRC, > EXPORT_SRC -- or by tools that have not yet been tied into the build, > such as warlock. > > * Source subtrees that will likely be resynched with an upstream entity > (e.g., sqlite). (This exception does not extend to unused build > infrastructure: upstream Makefiles and other unused build files are > forbidden since they are a hazard to those maintaining ON's actual > build infrastructure.) What about sources which are currently not used but will be used later ? For example there is "shcomp.c" in the ksh93-integration tree (and the exception list) which is used with a later putback (it was obmitted from the original putback since the shell script compiler may need something like "javaexec" which recognizes compiled shell code and runs it using ksh93 and the whole thing may be another extra-large ARC case... ;-( ) ... ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
