git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kacper Kornet <kornet@camk.edu.pl>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Johannes Sixt <j6t@kdbg.org>,
	Steffen Prohaska <prohaska@zib.de>
Subject: Re: [PATCH] Honor sysconfdir when set as an configure option
Date: Thu, 28 Apr 2011 23:22:18 +0200	[thread overview]
Message-ID: <20110428212218.GG4833@camk.edu.pl> (raw)
In-Reply-To: <7vzkna2ika.fsf@alter.siamese.dyndns.org>

On Thu, Apr 28, 2011 at 02:05:09PM -0700, Junio C Hamano wrote:
> Kacper Kornet <kornet@camk.edu.pl> writes:

> > ./configure can be run with option --sysconfdir=...
> > and Makefile should respect that choice.

> Thanks.  That statement is not wrong per-se, but your patch will result in
> git_etcdir always set to the same as $(sysconfdir) that is an absolute
> path, which in turn would mean that the build product with prefix set to
> something other than /usr won't relocate well, no?

Only when ./configure is used. But autotools do not support relative
paths, as far as I know. When autotools are not used, it is still
possible to have relative path in git_etcdir.

-- 
  Kacper Kornet

  reply	other threads:[~2011-04-28 21:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28  2:29 [PATCH] Respect definition of prefix from autotools in ETC_GITCONFIG and ETC_GITATTRIBUTES Kacper Kornet
2011-04-28 16:54 ` Junio C Hamano
2011-04-28 17:49   ` Kacper Kornet
2011-04-28 19:27   ` [PATCH 1/1] Honor $(prefix) set in config.mak* when defining ETC_GIT* and sysconfdir Kacper Kornet
2011-04-28 20:01     ` [PATCH] Honor sysconfdir when set as an configure option Kacper Kornet
2011-04-28 21:05       ` Junio C Hamano
2011-04-28 21:22         ` Kacper Kornet [this message]
2011-05-03  6:42     ` [PATCH 1/1] Honor $(prefix) set in config.mak* when defining ETC_GIT* and sysconfdir Johannes Sixt
2011-05-03 17:32       ` Junio C Hamano
2011-05-04  5:52         ` Johannes Sixt
2011-05-04 13:58           ` Kacper Kornet
2011-05-04 14:39             ` Johannes Sixt
2011-05-04 18:21               ` Junio C Hamano
2011-05-05  2:26                 ` Junio C Hamano
2011-05-05  5:58                   ` Johannes Sixt
2011-05-05 16:17                     ` Junio C Hamano
2011-05-06  7:03                       ` Johannes Sixt
2011-05-05 14:29                   ` Kacper Kornet
2011-05-05 14:45                     ` Johannes Sixt
2011-05-05 15:00                       ` Kacper Kornet
2011-05-05 15:46                         ` Junio C Hamano
2011-05-09  8:24                           ` Johannes Sixt
2011-05-09 11:56                             ` Kacper Kornet
2011-05-27  8:17                             ` Kacper Kornet
2011-05-05 15:25                       ` Kacper Kornet
2011-05-04 14:29         ` Kacper Kornet

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=20110428212218.GG4833@camk.edu.pl \
    --to=kornet@camk.edu.pl \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.org \
    --cc=prohaska@zib.de \
    /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).