On Wed, Aug 15, 2007 at 05:40:21PM -0400, Peter Memishian wrote:
>   7.5 Unreferenced File Policy
>   ============================
> 
>   An "unreferenced file" is a file that is not used during a build of a
>   given source tree.  An unreferenced file is considered a sign of
>   brokenness (in much the same manner as an unused variable flagged by
>   lint), and thus is forbidden in the ON source tree.  However, exceptions
>   may be granted by the gatekeepers when appropriate -- usually for:
> 
>      * READMEs and other textfiles that aid in understanding the source.
>        (Exceptions for these are automatically granted, provided the files
>        end in ".txt".)
> 
>      * 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.)
 [...]
> Comments?

What about tests that are in ON (e.g. usr/src/cmd/dtrace/test)?

Adam

-- 
Adam Leventhal, Solaris Kernel Development       http://blogs.sun.com/ahl
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to