From: "Matthias Andree" <matthias.andree@gmx.de>
To: "Junio C Hamano" <gitster@pobox.com>, "Johannes Sixt" <j6t@kdbg.org>
Cc: "Nanako Shiraishi" <nanako3@lavabit.com>, git@vger.kernel.org
Subject: Re: [PATCH v3] To make GIT-VERSION-FILE, search for git more widely
Date: Thu, 04 Jun 2009 10:35:58 +0200 [thread overview]
Message-ID: <op.uuzrh8jr1e62zd@balu.cs.uni-paderborn.de> (raw)
In-Reply-To: <7vvdnc37b6.fsf@alter.siamese.dyndns.org>
Am 04.06.2009, 07:18 Uhr, schrieb Junio C Hamano <gitster@pobox.com>:
> Johannes Sixt <j6t@kdbg.org> writes:
>
>> On Dienstag, 2. Juni 2009, Junio C Hamano wrote:
>>> Nanako Shiraishi <nanako3@lavabit.com> writes:
>>> > Junio, I think you forgot to take a follow-up action on this thread
>>> after
>>> > sending this message. The patch favors the git program in the
>>> current
>>> > directory.
>>>
>>> Indeed, I did, and I think I am Ok with the patch. Thanks for a
>>> reminder.
>>>
>>> I thought there was an "simplicity" issue raised by J6t that was not
>>> addressed, but after re-reading the thread I do not think it applies
>>> (J6t?)
>>
>> Sorry, I don't recall anymore what I said; but since the thread petered
>> out, I
>> use this patch in the repository where I share Matthias' 'sudo make
>> install'
>> problem:
>>
>> Subject: [PATCH] version-gen: Use just built git if no other git is in
>> PATH
>>
>> Signed-off-by: Johannes Sixt <j6t@kdbg.org>
>>
>> diff --git a/GIT-VERSION-GEN b/GIT-VERSION-GEN
>> index 39cde78..4779313 100755
>> --- a/GIT-VERSION-GEN
>> +++ b/GIT-VERSION-GEN
>> @@ -3,6 +3,9 @@
>> GVF=GIT-VERSION-FILE
>> DEF_VER=v1.6.3.GIT
>>
>> +# use git that was just compiled if there is no git elsewhere in PATH
>> +PATH=$PATH:.
>> +
>> LF='
>> '
>
> I actually think this is much saner and cleaner (it certainly is
> smaller),
> especially having seen Matthias's v4, which feels a tad overengineered.
It's nothing more than
(a) followed your suggestion to look in $(prefix) first for cross-building
support
(b) ported to git-gui as well (copy & paste-style)
Also, we certainly do not want to stuff "." in root's PATH, not even for
simple scripts like GIT-VERSION-GEN.
> I honestly do not understand why we need to bend backwards to cater to
> "sudo". Real men, when needing to do things as root, have always done
> "su", and _if_ the environment is unsuited for the job, they can do:
>
> $ su
> # PATH=$PATH:/usr/local/bin make prefix=/usr/local install
sudo caches passwords for a couple of minutes, su does not, and su isn't
available everywhere ("wheel" group on BSD and stuff); particularly, sudo
is *the* get-root-tool on Ubuntu.
If you argue "real men", then break that damn rebuild cycle and either fix
dependencies properly, rather than second-guessing in shell scripts at
"make install" time, or add post-update hooks (or whatever) to update the
GIT-VERSION-FILE...
"." doesn't belong in root's $PATH, period.
--
Matthias Andree
next prev parent reply other threads:[~2009-06-04 8:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 9:22 [PATCH v3] To make GIT-VERSION-FILE, search for git more widely Matthias Andree
2009-05-07 11:49 ` Michael J Gruber
2009-05-07 12:04 ` Matthias Andree
2009-05-07 12:09 ` Michael J Gruber
2009-05-07 12:12 ` Matthias Andree
2009-05-08 0:05 ` Junio C Hamano
2009-05-08 8:27 ` Matthias Andree
2009-05-08 8:41 ` Junio C Hamano
2009-05-08 11:09 ` Matthias Andree
2009-05-09 16:55 ` Junio C Hamano
2009-05-09 17:10 ` Francis Galiegue
2009-05-09 18:17 ` Matthias Andree
2009-05-13 12:17 ` Matthias Andree
2009-05-13 19:32 ` Junio C Hamano
2009-06-02 10:55 ` Nanako Shiraishi
2009-06-02 15:50 ` Junio C Hamano
2009-06-02 18:35 ` Johannes Sixt
2009-06-03 7:32 ` Matthias Andree
2009-06-04 0:12 ` [PATCH v4] " Matthias Andree
2009-06-04 5:18 ` [PATCH v3] " Junio C Hamano
2009-06-04 8:35 ` Matthias Andree [this message]
2009-05-08 8:52 ` Johannes Sixt
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=op.uuzrh8jr1e62zd@balu.cs.uni-paderborn.de \
--to=matthias.andree@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=nanako3@lavabit.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).