From: Sergio Callegari <scallegari@arces.unibo.it>
To: git@vger.kernel.org
Subject: Re: [PATCH] Only use ETC_GITCONFIG=$(prefix)/etc/gitconfig ifeq ($(prefix),$(HOME))
Date: Tue, 24 Apr 2007 09:05:36 +0000 (UTC) [thread overview]
Message-ID: <loom.20070424T105805-25@post.gmane.org> (raw)
In-Reply-To: 7v1wia9u02.fsf@assigned-by-dhcp.cox.net
> Junio C Hamano <junkio <at> cox.net> writes:
>
> > Josh Triplett <josh <at> freedesktop.org> writes:
> >
> >> ETC_GITCONFIG defaults to $(prefix)/etc/gitconfig, so if you just set
> >> prefix=/usr or prefix=/usr/local, you end up with a git that looks in
> >> /usr/etc/gitconfig or /usr/local/etc/gitconfig. That seems rather
suboptimal.
> >>
> Also what happens to people who use "prefix=/usr/local"?
>
Could it be better to set ETC_GITCONFIG=/etc/gitconfig /only/ if prefix is /usr?
These would possibly make all people who have git in /usr/local or in /opt/Git
or in /home happier...
If I am not wrong, /usr is the only prefix, where, for historical reasons
there is no /usr/etc but /etc is used. Having /usr/local/etc does not seem that
bad. And /opt/Git/etc appears surely ok.
Sergio
next prev parent reply other threads:[~2007-04-24 9:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 2:11 [PATCH] Only use ETC_GITCONFIG=$(prefix)/etc/gitconfig ifeq ($(prefix),$(HOME)) Josh Triplett
2007-04-24 4:27 ` Junio C Hamano
2007-04-24 5:44 ` Josh Triplett
2007-04-24 5:59 ` Junio C Hamano
2007-04-24 7:23 ` Josh Triplett
2007-04-24 7:51 ` [PATCH] Create a sysconfdir variable, and use it for ETC_GITCONFIG Josh Triplett
2007-04-24 8:12 ` Junio C Hamano
2007-04-24 6:08 ` [PATCH] Only use ETC_GITCONFIG=$(prefix)/etc/gitconfig ifeq ($(prefix),$(HOME)) Junio C Hamano
2007-04-24 6:17 ` Junio C Hamano
2007-04-24 9:05 ` Sergio Callegari [this message]
2007-04-24 6:19 ` Shawn O. Pearce
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=loom.20070424T105805-25@post.gmane.org \
--to=scallegari@arces.unibo.it \
--cc=git@vger.kernel.org \
/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).