From: "H.Merijn Brand" <h.m.brand@xs4all.nl>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Andy Dougherty <doughera@lafayette.edu>, git@vger.kernel.org
Subject: Re: [PATCH] Explain what 'ginstall' is
Date: Tue, 18 Dec 2007 08:38:43 +0100 [thread overview]
Message-ID: <20071218083843.42d7a15e@pc09.procura.nl> (raw)
In-Reply-To: <m3tzmgpzlu.fsf@roke.D-201>
On Mon, 17 Dec 2007 17:21:08 -0800 (PST), Jakub Narebski <jnareb@gmail.com>
wrote:
> 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.
And what if you OS *does* have an install, but one that is completely
useless^Wdifferent from the GNU install? Like the utterly useless
install on HP-UX.
> 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;
Yeah!
> 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.
Something like this? (gui part still missing). This is what I now
use
--8<--- make-install
#!/bin/sh
PREFIX=/pro/local
BINDIR=$PREFIX/bin
SHARED=$PREFIX/share
for p in git-fetch-pack git-hash-object git-index-pack git-fast-import \
git-daemon git-merge-index git-mktag git-mktree git-patch-id \
git-receive-pack git-send-pack git-shell git-show-index \
git-unpack-file git-update-server-info git-upload-pack \
git-pack-redundant git-var git-merge-tree git-imap-send \
git-merge-recursive git-bisect git-checkout git-clone \
git-merge-one-file git-mergetool git-parse-remote git-pull \
git-rebase git-rebase--interactive git-repack git-request-pull \
git-sh-setup git-am git-merge git-merge-stupid git-merge-octopus \
git-merge-resolve git-lost-found git-quiltimport git-submodule \
git-filter-branch git-stash git-add--interactive git-archimport \
git-cvsimport git-relink git-cvsserver git-remote git-cvsexportcommit \
git-send-email git-svn git-instaweb git-merge-subtree ; do
rm -f $BINDIR/$p
cp $p $BINDIR
chmod 755 $BINDIR/$p
done
cp git $BINDIR
cd templates
rm -rf $SHARED/git-core
mkdir $SHARED/git-core
mkdir $SHARED/git-core/templates
(cd blt && tar cf - .) | (cd $SHARED/git-core/templates/ && tar xf -)
cd ..
cd perl
make
make install UNINST=1
cd ..
for p in git-format-patch git-show git-whatchanged git-cherry \
git-get-tar-commit-id git-init git-repo-config git-fsck-objects \
git-cherry-pick git-peek-remote git-status git-add git-annotate \
git-apply git-archive git-blame git-branch git-bundle git-cat-file \
git-check-attr git-checkout-index git-check-ref-format git-clean \
git-commit git-commit-tree git-count-objects git-describe git-diff \
git-diff-files git-diff-index git-diff-tree git-fast-export \
git-fetch git-fetch-pack git-fetch--tool git-fmt-merge-msg \
git-for-each-ref git-fsck git-gc git-grep git-init-db git-log \
git-ls-files git-ls-tree git-ls-remote git-mailinfo git-mailsplit \
git-merge-base git-merge-file git-merge-ours git-mv git-name-rev \
git-pack-objects git-prune git-prune-packed git-push git-read-tree \
git-reflog git-send-pack git-config git-rerere git-reset \
git-rev-list git-rev-parse git-revert git-rm git-shortlog \
git-show-branch git-stripspace git-symbolic-ref git-tag git-tar-tree \
git-unpack-objects git-update-index git-update-ref \
git-upload-archive git-verify-pack git-verify-tag git-write-tree \
git-show-ref git-pack-refs ; do
rm -f $BINDIR/$p
ln $BINDIR/git $BINDIR/$p
done
-->8---
--
H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using & porting perl 5.6.2, 5.8.x, 5.10.x on HP-UX 10.20, 11.00, 11.11,
& 11.23, SuSE 10.1 & 10.2, AIX 5.2, and Cygwin. http://qa.perl.org
http://mirrors.develooper.com/hpux/ http://www.test-smoke.org
http://www.goldmark.org/jeff/stupid-disclaimers/
next prev parent reply other threads:[~2007-12-18 7:39 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 [this message]
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=20071218083843.42d7a15e@pc09.procura.nl \
--to=h.m.brand@xs4all.nl \
--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).