Darren J Moffat <[EMAIL PROTECTED]> writes: > Joerg Schilling wrote: >> Peter Memishian <[EMAIL PROTECTED]> wrote: >> >>> Folks, >>> >>> During the ksh93 code review, the topic of policies for unreferenced files >>> in ON came up. As per http://opensolaris.org/os/community/on/findunref >>> we've had an internal policy since March 2001 that unreferenced files are >>> generally not permitted, but it's not covered in any of the OpenSolaris >>> development literature that I'm aware of. As such, I've put together the >>> following write-up, which I propose including in the "Best Practices and >>> Requirements" section of http://opensolaris.org/os/community/on/devref_toc >>> >>> 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: >> >> If you like to integrate _Portable_ OSS from other sources, you would need >> to live with _aparently_ unused files. > > I don't see how that follows. In fact including externally maintained > upstream source in ON often isn't a good idea at all. >
I would suggest it doesn't follow, be the source in ON (or, possibly, elsewhere) it would still be merely dead code, on our side of things given it has to work in exactly one place, the release-in-progess. -- Rich _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
