> Does this mean that there is no problem with files from portable software that > are only apparently unreferenced when checking the Solaris platform variant > but > ignoring other platforms?
Just to clarify, we're not talking about "apparently" unreferenced files here. We're talking about files that have been demonstrated to be unreferenced during a full build on both sparc and x86 architectures. If code is explicitly for other platforms, it is not "apparently unreferenced." It is obviously expected to be unreferenced. We're also not talking about portability here, because we're explicitly talking about code that was only ever intended to be compiled on a single platform. Whether such code fits the likely-to-be-synced-upstream exception is an interesting discussion, and I think that's what you're asking above. And there, my initial impression is that any such inclusion will provide a false sense of security. If somebody in ON changes a header file in a way that will break such code, it will never be discovered in an ON build. If somebody is syncing upstream, they will not be doing so directly from an ON repository. (Because they won't be syncing ON makefiles, etc.) I think an upstream sync necessarily implies pulling the current upstream source, integrating your changes, and building it OUTSIDE of the context of ON. Anything else is negligent. Including the unused-in-ON code provides no benefits that are immediately obvious to me. --Mark _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
