zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <zefram@fysh.org>
To: schaefer@candle.brasslantern.com (Bart Schaefer)
Cc: schizo@debian.org, zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: 3.1.6 install without rebuild (Re: 3.0 DESTDIR)
Date: Sun, 24 Oct 1999 22:04:07 +0100 (BST)	[thread overview]
Message-ID: <E11fUoB-0007l4-00@crucigera.fysh.org> (raw)
In-Reply-To: <991024175838.ZM6757@candle.brasslantern.com> from Bart Schaefer at "Oct 24, 1999  5:58:38 pm"

Bart Schaefer wrote:
>This means that "make MODDIR=/some/new/path fndir=/some/other/new/path"
>does not recompile zsh,

I intentionally wrote that code so that that *would* cause a recompile.
make MODDIR=foo guarantees to build a zsh which has the module directory
specified.  After your patch, changing MODDIR for make results in a zsh
with indeterminate module directory.  You would require a "make clean"
to reliably change the module directory, when in reality only a couple of
files need to be rebuilt.  (I'm operating under a more general principle
that the final result of make should be the same regardless of files
already built; make's job is simply to minimise the amount that gets
rebuilt, reusing a partial build if possible.)

Btw, my view is that giving different parameters to "make install"
from those one gave to "make" is a bad practice, but if it is to be
supported then the parameters from "make install" must take precedence.
After all, those are the parameters that will take effect if anything
changes and gets rebuilt during the "make install".

All of this is a matter of "least surprise", too.

>I'm now considering backing out the $DESTDIR stuff, because with this patch
>you can do this kind of thing (which works in 3.0.7 as well, by the way):
>
>	configure --prefix='${INSTROOT}/usr/local'
>	make
>	make INSTROOT=/tmp/zshtest install

Surely you're joking, Mr Schaefer.  OK, that's a nice hack, but DESTDIR
is a whole lot clearer.  Let's keep configured pathnames and install
paths properly distinct.

-zefram


  reply	other threads:[~1999-10-24 21:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-19  5:22 Patch: 3.1.6-bart-7: Another rlimit Bart Schaefer
1999-10-19  6:13 ` PATCH: " Bart Schaefer
1999-10-20 20:17   ` Zefram
1999-10-21  1:53     ` Bart Schaefer
1999-10-24  0:45   ` 3.0 DESTDIR Clint Adams
1999-10-24  1:55     ` Bart Schaefer
1999-10-24  5:05       ` Clint Adams
1999-10-24  6:20         ` Bart Schaefer
1999-10-24 14:30           ` Clint Adams
1999-10-24 14:51             ` Bruce Stephens
1999-10-27  2:17               ` Clint Adams
1999-10-24 17:58             ` PATCH: 3.1.6 install without rebuild (Re: 3.0 DESTDIR) Bart Schaefer
1999-10-24 21:04               ` Zefram [this message]
1999-10-24 21:55                 ` Bart Schaefer
1999-10-24 21:57                 ` Bart Schaefer
1999-10-28  1:58               ` Juergen A. Erhard
1999-10-28  3:31                 ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E11fUoB-0007l4-00@crucigera.fysh.org \
    --to=zefram@fysh.org \
    --cc=schaefer@candle.brasslantern.com \
    --cc=schizo@debian.org \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).