On Wed, 4 Jun 2003 16:23:17 +0200
Alistair Crooks <agc@wasabisystems.com> wrote:

> On Tue, Jun 03, 2003 at 04:37:18PM -0400, Jan Schaumann wrote:
> > Alistair Crooks <agc@wasabisystems.com> wrote:
> > > On Tue, Jun 03, 2003 at 03:40:13PM -0400, Jan Schaumann wrote:
> > > > Extensive documentation (often in form of HTML docs) is often available
> > > > for several packages, but not everybody may want to install it.  Rather
> > > > than creating variables for each package, should we create a variable
> > > > that can be set to, say, "all", "html", "pdf", "ps" or some combination
> > > > so that packages can check that variable?
> > > 
> > > And manipulate the PLISTS... how, exactly?
> > 
> > .if ${INSTALL_DOCS:Mhtml}
> > PLIST_SRC+=	${WRKSRC}/PLIST.html
> > .endif
> 
> Yup, that sounds good to me, in principle (although I think I'd
> s/WRKSRC/FILESDIR/, since it's more than likely that we're managing
> the PLIST.html file)

Couldn't this be handled automatically from bsd.pkg.mk, when generating
the ${WRKDIR}/.PLIST file?  In fact, to avoid registering it (and assuming
1) the package does not install the html's, 2) html's are installed in the
right place), one should only 'grep -v ^share/doc/html/' and directories
with 'grep -v "^@dirrm share/doc/html/'.  Isn't it?

Cheers

-- 
Julio M. Merino Vidal <jmmv@menta.net>
The NetBSD Project - http://www.NetBSD.org/