From owner-freebsd-ports Wed Feb 28 03:59:51 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA04170 for ports-outgoing; Wed, 28 Feb 1996 03:59:51 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA04154 for ; Wed, 28 Feb 1996 03:59:48 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.4/8.6.9) id DAA00921; Wed, 28 Feb 1996 03:59:29 -0800 (PST) Date: Wed, 28 Feb 1996 03:59:29 -0800 (PST) Message-Id: <199602281159.DAA00921@silvia.HIP.Berkeley.EDU> To: chuckr@Glue.umd.edu CC: thomas@ghpc8.ihf.rwth-aachen.de, adam@veda.is, freebsd-ports@freebsd.org In-reply-to: (message from Chuck Robey on Tue, 27 Feb 1996 18:15:14 -0500 (EST)) Subject: Re: doc directory From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-ports@freebsd.org Precedence: bulk * > I think it should be enough to set ${PORTSDOCDIR} to * > ${PREFIX}/share/doc/${PKGNAME} and add it to the exported variables * > for the various scripts and the Makefile in ${WRKSRC}. * * I wanted the change, too. From what I understood (and I could have been * wrong) Satoshi was telling me if I wanted such a thing, code it in each * ports makefile, that it wasn't needed to change bsd.port.mk. I * disagreed, but I don't trust myself to make changes in bsd.port.mk (what * a tangle!) so I let it lie. That is correct (that I said that). The reason why I don't see the necessity to add a new variable for this is because we need to put the explicit directory name in pkg/PLIST (no variable substitutions here) anyway. In a nutshell, what I was thinking was: (1) Add "share/doc" to /etc/mtree/BSD.local.dist so that the directory is created by mtree (2) Porters will add a post-install target that will create ${PREFIX}/share/doc/${PKGNAME} and copy doc files in there (3) Also, add "share/doc/${PKGNAME}/${FILES}" in pkg/PLIST (note ${PKGNAME} and ${FILES} should be substituted by the porter) (1) is what Adam suggested (pretty much). Chuck's proposal helps (2) but not (3), and since the porter needs to know the exact directory name anyway, it is even rather confusing (why do they need to learn about another variable when we already have too many? :> ). Satoshi