Date: Fri, 07 Jan 2005 10:09:24 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: paul@originative.co.uk Cc: colin.percival@wadham.ox.ac.uk Subject: Re: cvs commit: src/share/man/man9 style.9 Message-ID: <20050107.100924.112818131.imp@bsdimp.com> In-Reply-To: <20050107111311.GC18004@myrddin.originative.co.uk> References: <20050106101233.GL16316@myrddin.originative.co.uk> <20050106.122059.74757197.imp@harmony.village.org> <20050107111311.GC18004@myrddin.originative.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20050107111311.GC18004@myrddin.originative.co.uk>
Paul Richards <paul@originative.co.uk> writes:
: On Thu, Jan 06, 2005 at 12:20:59PM -0700, Warner Losh wrote:
: >
: > I've actually given the matter a lot of thought, and simpler
: > definitely is better here. There are too many different kinds of
: > licenses in the tree (hundreds of variations to the standard BSD
: > license, the mit license, and all the my little pony licenses that
: > likely will be headache for us one day) to do anything other than
: > <license> </license>, which is what the - tag does for us
: > unobtrusively.
:
: Yeah, that's what I'd have assumed for the license but there are
: probably other things that could be marked up for processing as
: well. I think Doug's been using Doxygen in some places in the tree.
I think Doxygen is a great tool, and we should use it more. However,
it isn't the right tool for this job...
: > Having said that, if you are willing to step to the plate and do the
: > work necessary to make a more complex scheme work, be my guest. I'm
: > not presently planning on doing that.
:
: I don't mind doing some work in this area. My choice would be to
: use XML though since that's an universal technology that we're
: beginning to use in lots of other places as well, so to me it would
: make sense to keep to the one technology.
Adopting XML for XML's sake is silly. Had I done that, I'd have to
commit to every single file, since nothing used that yet. As it was,
I had to touch maybe 65% of the tree. The up side is that now I have
a long list of files that have some issue or another with their
notices... Also, like I said, there's no standard here. This project
uses these tags, that project uses other tags. It would be hard to
get anything 'complicated' integrated into other system, so I went
with the simplest solution possible.
A coworker wrote a command that nicely harvests all of the License
notices, eliminates some of the mindless duplication, leaving only
other kinds of duplication to worry about...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050107.100924.112818131.imp>