public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Kacper Kornet <kornet@camk•edu.pl>
To: Johannes Sixt <j.sixt@viscovery•net>
Cc: Junio C Hamano <gitster@pobox•com>, git@vger•kernel.org
Subject: Re: [PATCH 1/1] Honor $(prefix) set in config.mak* when defining ETC_GIT* and sysconfdir
Date: Wed, 4 May 2011 15:58:27 +0200	[thread overview]
Message-ID: <20110504135827.GC18585@camk.edu.pl> (raw)
In-Reply-To: <4DC0E99E.6090402@viscovery.net>

On Wed, May 04, 2011 at 07:52:30AM +0200, Johannes Sixt wrote:
> Looking closer, the patch introduces git_etcdir for no good reason,
> IIUC.
> It should just re-use sysconfdir (the meaning of this variable is to
> point
> to the etc directory).

And the first version of my patch did it. However Junio has written:

> But this part in the Makefile outside the context of the patch bothers
> me.  It seems to imply that sysconfdir is _not_ that variable you want
> to
> define later.
>
>    # Among the variables below, these:
>    #   gitexecdir
>    #   template_dir
>    #   mandir
>    #   infodir
>    #   htmldir
>    #   ETC_GITCONFIG (but not sysconfdir)
>    #   ETC_GITATTRIBUTES
>    # can be specified as a relative path some/where/else;
>
> So I have a suspicion that your patch as is will break when prefix is
> set
> to something other than /usr directory.  I don't think anybody in-tree
> currently uses sysconfdir, but that does not mean nobody will ever do.

>From that I understood that he prefers sysconfdir to be always an
absolute path.
-- 
  Kacper Kornet

  reply	other threads:[~2011-05-04 13:58 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
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 [this message]
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=20110504135827.GC18585@camk.edu.pl \
    --to=kornet@camk$(echo .)edu.pl \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=j.sixt@viscovery$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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