>>>>> "meem" == Peter Memishian <peter.memishian at sun.com> writes:
Roland> Fixed (I wish we could keep the comments to document how this Roland> stuff was created... ;-( ). meem> They can go in the CR used to integrate the feature. Actually, meem> they can go pretty much anywhere *except* the source tree. Roland> There is still the unanswered/unsolved problem to track such Roland> things... any CR documentation is AFAIK not public and (more Roland> important) not maintained by a SCM (and even if there is such a Roland> SCM it would need to be kept in sync with the main OS/Net SCM, Roland> following all branches, splits, mergers etc.). meem> The fact that it's not public is a bug which is being worked. Yes, but very slowly, and with occasional regressions. At the moment, the only two text fields that are visible externally are Description and Workaround. I don't know when attachments will be available externally. For now, I think the only workable choices for things like this are (a) in the source tree (e.g., as a readme), or (b) on the project's web page on opensolaris.org. I'm okay with either, though if it goes on a web page, there needs to be a pointer in the source tree (e.g., a README). >> > > > usr/src/lib/libdll/common/Makefile [...] Roland> The Makefile isn't used, it's just there (well, until now it Roland> didn't bite anyone). meem> I'm glad to hear it's not used. However, the name alone makes it meem> an attractive nuisance -- and a possible victim of automated meem> Makefile updates (e.g., when we changed all instances of "-v" to meem> "$(CCVERBOSE)"). Yes, I would prefer that something else be done with the new <library>/common/Makefile files. Someone who's familiar with the ON makefiles and build conventions will probably be able to deduce that they're not used, but otherwise they're just going to confuse people. mike
