From: Jakub Narebski <jnareb@gmail•com>
To: Andy Dougherty <doughera@lafayette•edu>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] Explain what 'ginstall' is
Date: Mon, 17 Dec 2007 17:21:08 -0800 (PST) [thread overview]
Message-ID: <m3tzmgpzlu.fsf@roke.D-201> (raw)
In-Reply-To: <Pine.LNX.4.64.0712171641370.24957@fractal.phys.lafayette.edu>
Andy Dougherty <doughera@lafayette•edu> writes:
> [...]. Perhaps configure
> should just go looking for a suitable install program instead of
> assuming everyone has one.
First, configure is, and (I think) consensus is that it should remain
optional. This means that Makefile "guess" section should have good
defaults for your operating system.
Second, the default autoconf macro AC_PROG_INSTALL *requires* that
there is BSD-compatible `install' program (as 'install-sh' or
'install.sh') in the sources. Adding such script is (I think) not a
problem; finding minimal portable[*1*] script is. So if you know
one...
Footnotes:
----------
[*1*] By "portable" I mean here 'git portable', i.e. requiring only
those shell constructs/features that git require, not necessary
insanelt portable the way ./configure script is.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-12-18 1:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 21:46 [PATCH] Explain what 'ginstall' is Andy Dougherty
2007-12-18 1:21 ` Jakub Narebski [this message]
2007-12-18 7:38 ` H.Merijn Brand
2007-12-18 8:20 ` Jakub Narebski
2007-12-18 8:38 ` H.Merijn Brand
2007-12-18 9:14 ` Jakub Narebski
2007-12-18 11:11 ` H.Merijn Brand
2007-12-18 12:32 ` Jakub Narebski
2007-12-18 13:32 ` H.Merijn Brand
2007-12-18 14:03 ` Jakub Narebski
2007-12-18 14:27 ` H.Merijn Brand
2007-12-23 9:01 ` Jan Hudec
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=m3tzmgpzlu.fsf@roke.D-201 \
--to=jnareb@gmail$(echo .)com \
--cc=doughera@lafayette$(echo .)edu \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox