Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 2 Mar 1996 00:03:39 -0500 (EST)
From:      Chuck Robey <chuckr@Glue.umd.edu>
To:        Satoshi Asami <asami@cs.berkeley.edu>
Cc:        adam@veda.is, thomas@ghpc8.ihf.rwth-aachen.de, freebsd-ports@freebsd.org
Subject:   Re: doc directory
Message-ID:  <Pine.OSF.3.91.960302000038.7699A-100000@skipper.eng.umd.edu>
In-Reply-To: <199603012121.NAA01260@sunrise.cs.berkeley.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 1 Mar 1996, Satoshi Asami wrote:

>  * > (1) Add "share/doc" to /etc/mtree/BSD.local.dist so that the directory 
>  * >     is created by mtree
>  * 
>  * Yes, this is what I was suggesting, and there seems to be agreement that
>  * share/doc is preferable to plain doc. Please may I commit this now? :)
> 
> Yes, I think we've seen no objections.
> 
>  * Looks reasonable. Another good reason to keep it out of bsd.port.mk
>  * is that ${DISTNAME} and ${PKGNAME} usually carry a version number,
>  * but ${DOCDIR} could be something else entirely (for instance
>  * without the version number, or simply
> 
> That's right, this can be anything that the port desires.
> 
> Actually, I think it's better to leave out the version number for most
> cases.  If you have a version number in the directory name, when you
> upgrade a port, you will have to change pkg/PLIST to reflect it, and I
> can see people forgetting it (and me not noticing it because "make
> package" will happily use the old docs!).
> 
> The exception of course is things like tcl/tk, where having multiple
> versions of the same software makes sense.  Usually, the installation
> of the new version will overwrite the binary/library etc., anyway, so
> there is not much use in keeping a separate directory for old
> documents....

If you guys are going to do this, and not document it by making changes 
that porters would find in bsd.port.mk, then I think you are going to 
have to put this into the handbook.  Just to make sure I understood 
everything right, this is NOT for ports man pages, this is for the extra 
things most ports have lying around, like READMEs and various freeform docs.
If you don't, then just the folks reading this thread will know this (and 
my memory is SHORT!)


==========================================================================
Chuck Robey chuckr@eng.umd.edu, I run FreeBSD-current on n3lxx + Journey2
 
Three Accounts for the Super-users in the sky,
  Seven for the Operators in their halls of fame,
Nine for Ordinary Users doomed to crie,
  One for the Illegal Cracker with his evil game
In the Domains of Internet where the data lie.
  One Account to rule them all, One Account to watch them,
  One Account to make them all and in the network bind them.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.3.91.960302000038.7699A-100000>