Date: Mon, 9 Jun 1997 16:21:27 -0700 (PDT) From: "Brian N. Handy" <handy@sag.space.lockheed.com> To: ports@freebsd.org Subject: Re: ports/doc question Message-ID: <Pine.OSF.3.96.970609160549.14353O-100000@sag.space.lockheed.com> In-Reply-To: <199706092220.PAA01028@vader.cs.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> [I have an optional "make install.doc" target.] >Assuming you mean DOCDIR=/usr/local/share/doc, you are right. > > * (2) This is an optional target. How do other ports deal with this > * possibility? I'm wondering how the PLIST is supposed to work out, if > * I want to install the documentation. The package certainly works > * fine without this stuff. Should I ignore it? > >See the handbook. :) That's NOPORTDOCS. Ah yes, I see this now. I've now figured out how to install the docs. Move along with me to the PLIST, if you will... The first part of the plist is based on a PREFIX of /usr/local, but now I've got all these files in /usr/share. So I have, say bin/gv lib/X11/app-defaults/GV [...] But now, I need something like @cwd /usr/share/doc gv/gv-1.html gv/gv-2.html [...] --> but this give me a hard-coded link in the makefile. Should this instead be @cwd $(DOCDIR) or ... something else? I'm not sure how best to cope with this. The man page for pkg_create was tantalizingly close to explaining how to do this, but no joy. Thanks Brian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.3.96.970609160549.14353O-100000>