Mark J. Nelson writes: > > A simple text file delivered with SUNWonbld sounds like a start. > > /opt/onbld/etc/comment.reg? > > Hm. Now there are two questions: > > 1. Where should this go? > > 2. Should this be packaged? > > For where it goes, I don't like putting it in ON. It's not an artifact > of ON.
It's no more or less an artifact of ON than is Cdm.py or a pile of other things in SUNWonbld. So? Yes, I think someone could refactor SUNWonbld into "generally nifty tools that should be used for all gates" (SUNWgnttsbufag) and an ON-specific SUNWonbld. But I'm not sure I see why that tool refactoring is necessarily a gating item for the relatively simple upgrade to webrev that you're talking about. > It might seem like overkill to have a single-purpose repository, > but the burden of operating such a thing would be extremely small. > For packaging, it's not a bad idea for SUNWonbld to include this info, > because it also includes at least one tool (webrev) that will be > dependent on it. Can we reasonably do that, and explicitly defer being > the authoritative source of such info? I think that separating out the things that can be used outside of ON (such as at least the Cadmium extensions and webrev itself) is a bit of work distinct from making webrev easily extensible for different bug repositories. -- James Carlson, Solaris Networking <james.d.carl...@sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
