All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santi <sbejar@gmail.com>
To: "Yakov Lerner" <iler.ml@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] auto-detect changed $prefix in Makefile and properly rebuild to avoid broken install
Date: Thu, 15 Jun 2006 14:49:12 +0200	[thread overview]
Message-ID: <8aa486160606150549n4b55912ap@mail.gmail.com> (raw)
In-Reply-To: <f36b08ee0606150440l544455c7r5c52609b360d0f74@mail.gmail.com>

2006/6/15, Yakov Lerner <iler.ml@gmail.com>:
> On 6/15/06, Santi <sbejar@gmail.com> wrote:
> > Wed, 14 Jun 2006 22:26 +0300, Yakov Lerner <iler.ml@gmail.com>:
> > > Many times, I mistakenly used 'make prefix=... install' where prefix value
> > > was different from prefix value during build. This resulted in broken
> > > install. This patch adds auto-detection of $prefix change to the Makefile.
> > > This results in correct install whenever prefix is changed.
> >
> > I do this each time I install packages from source. I keep them with
> > "stow" and the usual sequence is:
> >
> > make prefix=/home/santi/usr
> > make install prefix=/home/santi/usr/stow/git
> > cd /home/santi/usr/stow/
> > stow -v git
> >
> > so with this auto-detection I'll compile some programs twice.
>
> I'm not familiar with stow. Does stow create some kind of symlinks from
> /home/santi/usr/stow/git to home/santi/usr ?
It makes links from .../usr/ to .../usr/stow/git/, for expample:

$ls -l ~/usr/bin/git
lrwxrwxrwx 1 santi santi 19 2006-06-01 09:42 /home/santi/usr/bin/git
-> ../stow/git/bin/git*


> If so, why can't you
> use prefix=/home/santi/usr/stow/git both in 'make' and in 'make install' ?
> Would this work ?

For the few tests I've made it does works, but it is not the
recommended method from the stow developers, and I suppose they know
better than me.

>
> BTW, is it possible to have git use argv[0] to automatically determine
> the executable_dir without compiled-in paths ?
>
> Yakov
>

  reply	other threads:[~2006-06-15 12:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14 19:26 [PATCH] auto-detect changed $prefix in Makefile and properly rebuild to avoid broken install Yakov Lerner
2006-06-14 20:04 ` Junio C Hamano
2006-06-14 20:30   ` Yakov Lerner
2006-06-14 21:32     ` Junio C Hamano
2006-06-14 21:38       ` Yakov Lerner
2006-06-15  9:26         ` Matthias Lederhofer
2006-06-15 11:11           ` Yakov Lerner
2006-06-18 13:31   ` Petr Baudis
2006-06-15 11:26 ` Santi
2006-06-15 11:40   ` Yakov Lerner
2006-06-15 12:49     ` Santi [this message]
2006-06-15 13:00       ` Alexander Litvinov
2006-06-17  5:28     ` Junio C Hamano
2006-06-17  5:26   ` Junio C Hamano
2006-06-18 11:24     ` Karl Hasselström
2006-06-18 11:47       ` Junio C Hamano
2006-06-18 14:44         ` Karl Hasselström

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=8aa486160606150549n4b55912ap@mail.gmail.com \
    --to=sbejar@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=iler.ml@gmail.com \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.