From: Junio C Hamano <junkio@cox.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] autoconf: Add checking for BSD-compatibile 'install' program
Date: Thu, 07 Sep 2006 13:21:36 -0700 [thread overview]
Message-ID: <7v8xkvxwa7.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200609071431.18343.jnareb@gmail.com> (Jakub Narebski's message of "Thu, 7 Sep 2006 14:31:18 +0200")
Jakub Narebski <jnareb@gmail.com> writes:
> Uncomment `AC_PROG_INSTALL' macro in configure.ac, and setting
> `INSTALL' variable in config.mak.in
>
> Add `install-sh' shell script (required when using `AC_PROG_INSTALL'
> macro) scriptversion=2005-11-07.23, taken from KDE SDK 3.5.3.
>
> Signed-off-by: Jakub Narebski <jnareb@gmail.com>
> ---
> Perhaps `install-sh' script should be replaced by something simplier,
> for example by script which was sent to git mailing list, but AFAIK
> not accepted.
That somehow sounds like whining. I do not think it was never
proposed for inclusion but was just offered as a friendly
"somebody else might find it useful".
In any case, I have two issues, but one non-issue first. I am
not opposed to including install-sh that is maintained somewhere
upstream and GPLv2 compatible.
- I do not particularly like to have too many autoconf related
cruft at the toplevel, and I am wondering if we can move it
to say compat/install-sh.
- I suspect this fall-back would set "INSTALL = ./install-sh"
(if you have it in compat, "INSTALL = compat/install-sh"). I
wonder if it breaks builds in subdirectories
(i.e. Documentation/ and templates/).
next prev parent reply other threads:[~2006-09-07 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 12:31 [PATCH] autoconf: Add checking for BSD-compatibile 'install' program Jakub Narebski
2006-09-07 20:21 ` Junio C Hamano [this message]
2006-09-07 21:39 ` Jakub Narebski
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=7v8xkvxwa7.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jnareb@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 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).