Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 25 Nov 2000 12:52:28 -0600 (CST)
From:      Mike Meyer <mwm@mired.org>
To:        Sheldon Hearn <sheldonh@uunet.co.za>, Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc:        cvs-all@freebsd.org
Subject:   Re: cvs commit: src/share/man/man5 make.conf.5 src/share/man/man7 build.7 
Message-ID:  <14880.2668.179221.326951@guru.mired.org>
In-Reply-To: <42577.975172353@axl.fw.uunet.co.za>
References:  <42577.975172353@axl.fw.uunet.co.za> <200011251739.eAPHdke20159@troutmask.apl.washington.edu> <14878.49285.387120.103524@guru.mired.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Steve Kargl <sgk@troutmask.apl.washington.edu> types:
> Sheldon Hearn wrote:
> > > On a larger scale, is there a rational for having these things be two
> > > document repositories at all?
> > I think that manual pages are designed to document utilities, interfaces,
> > formats and drivers.  I think that the handbook is designed to document
> > more general processes that may or may not include the use of more than
> > one utility, interface, driver or format.
> This sounds reasonable, except the handbook isn't built and
> installed on your system after "make world" while man pages
> are.  AFAIK, the tools required to buld and read the handbook
> are not part of the base system.
> 
> "man rc.conf" brings up a page that can be read.  "man handbook"
> does not work, "handbook handbook" doesn't work, "info handbook"
> does not work.

Those are all true (you have to install the docjproj port to get all
the tools to build the handbook). I think I mentioned them as reasons
for having these things as man pages in the PR that had them.

However Sheldon pretty much nailed it on the head:

Sheldon Hearn <sheldonh@uunet.co.za> types:
> On Fri, 24 Nov 2000 13:24:53 CST, Mike Meyer wrote:
> > That's the kind of thing that strikes me as a bad idea without a clear
> > and obvious reason for doing so.
> You're probably right.  Now take a step back and behold the mountain
> that you plan to scale. :-)

Yup. At the very least, it's a long-term project. The implications for
the web site need to be considered as well.

However, given that over half my PRs that include fixes, documentation
or new code tend to sit ignored for months, I have almost zero
inclination to tackle even a small project at this point.

	<mike
--
Mike Meyer					http://www.mired.org/home/mwm/
Freelance WWW/Unix/FreeBSD consultant,		email for rates.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14880.2668.179221.326951>