Date: Sun, 23 Apr 95 02:25:41 +0100 From: jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi) To: jkh@freefall.cdrom.com 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: <9504230125.AA16623@cabri.obs-besancon.fr> In-Reply-To: <6311.798591756@freefall.cdrom.com> (jkh@freefall.cdrom.com)
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Jordan" == Jordan K Hubbard <jkh@freefall.cdrom.com> writes:
>> Are you crazy guys? This change implies that PREFIX can't be set to
>> anything different from /usr/local. In this case it is even better to
>> remove all references to PREFIX and replace them with /usr/local :-(
>>
>> This is a big step backwards!
> Not actually..
> Think about it, Jean-Marc..
> What everyone's been doing up to now has been to put little rules like:
> pre-install:
> @mkdir -p ${PREFIX}/bin
> @mkdir -p ${PREFIX}/lib
> ...
> Into their Makefiles. Sure, they don't mention /usr/local directly,
> but they're creating the _same underlying hierarchy_! So you redirect
> your prefix to /usr/foo - you're STILL going to be expected to have
> things like /usr/foo/lib and /usr/foo/man/man1!
> All I did with the BSD.local.dist change was centralize this. It's
> run for ALL values of ${PREFIX} except ${X11BASE}, which we know
> follows a different structure and should already be created as part of
> the XFree86 installation (if this turns out not to be the case then
> we'll have to create an XFree86.dist or something!).
> I don't see how this constitutes a step backwards at all. Sure
> BSD.local.dist is inappropriately named in the case where
> PREFIX=/usr/foo, but it certainly doesn't bother me enough to lose
> sleep over.
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.
Removing those rules simply because they are "ugly" is not a valid
argument (IMHO). They add versatility to the ports.
What about another variable? For example:
MAKEDIRS= bin man/man1 lib/whatever
removing the pre-install ugliness , and adding some more magic in
bsd.port.mk?
> Jordan
Jean-Marc
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
Jean-Marc Zucconi | jmz@cabri.obs-besancon.fr
Observatoire de Besancon |
F 25010 Besancon cedex | PGP Key: finger jmz@cabri.obs-besancon.fr
=========================================================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9504230125.AA16623>