Date: Sat, 22 Apr 1995 17:46:17 -0700 From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com> To: jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi) Cc: asami@cs.berkeley.edu, jkh@time.cdrom.com, CVS-commiters@time.cdrom.com, cvs-other@time.cdrom.com Subject: Re: cvs commit: /host/freefall/a/ncvs/ports/lang/forth Makefile Message-ID: <8069.798597977@freefall.cdrom.com> In-Reply-To: Your message of "Sun, 23 Apr 95 02:25:41 BST." <9504230125.AA16623@cabri.obs-besancon.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
> There is no problem if you have only one 'local' hierarchy, but what > if you want to install ports in several different locations? Of course > it is also possible to create a full tree for each location, but > creating 15-25 subdirectories when I only need /usr/foo/bin and > /usr/foo/man/man1 is not the best solution. I still don't think you understand. pkg_add will create the complete hierarchy for you if you install a port package. I fully expect some part of the generic install framework to do the same thing (since we're trying to keep the behavior of `pkg_add' and `make install' in sync here, right?). Sure, the user probably gets a lot more directories in /usr/foo than they expected, but that's the breaks. I think the gain is worth it. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8069.798597977>