git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Hudec <bulb@ucw.cz>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Andy Dougherty <doughera@lafayette.edu>, git@vger.kernel.org
Subject: Re: [PATCH] Explain what 'ginstall' is
Date: Sun, 23 Dec 2007 10:01:45 +0100	[thread overview]
Message-ID: <20071223090145.GB3563@efreet.light.src> (raw)
In-Reply-To: <m3tzmgpzlu.fsf@roke.D-201>

On Mon, Dec 17, 2007 at 17:21:08 -0800, Jakub Narebski wrote:
> [...]
> 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...

What's wrong with the one that comes with automake? It should be portable
the insane way ./configure script is -- which should be at least as much as
git -- and the license is compatible (MIT/X).

> 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.

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>

      parent reply	other threads:[~2007-12-23  9:02 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
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 [this message]

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=20071223090145.GB3563@efreet.light.src \
    --to=bulb@ucw.cz \
    --cc=doughera@lafayette.edu \
    --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).