All of lore.kernel.org
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: RE: [BUG] PREFIX environment variable ignored by git config --system
Date: Wed, 29 Jan 2025 12:01:19 -0500	[thread overview]
Message-ID: <008201db726f$6e6990b0$4b3cb210$@nexbridge.com> (raw)
In-Reply-To: <xmqqbjvpk1wo.fsf@gitster.g>

On January 29, 2025 11:42 AM, Junio C Hamano. Wrote:
><rsbecker@nexbridge.com> writes:
>
>> Thank you for filling out a Git bug report!
>>
>> Please answer the following questions to help us understand your issue.
>>
>> What did you do before the bug happened? (Steps to reproduce your
>> issue) export PREFIX=/home/randall git config --system --list
>>
>> What did you expect to happen? (Expected behavior) Git should use
>> ${PREFIX}/etc/gitconfig instead of the build location to
>
>But that is now how PREFIX works, as far as I remember.  PREFIX is a
build-time
>thing.
>
>Perhaps you are looking for RUNTIME_PREFIX build-time option?  I do not
know
>how well it is maintained these days, and if it allows you to futz with the
paths at
>runtime (without _moving_ the executable and all other installation
material en
>masse), though.

The documentation on the Environment Configuration page seems to imply that
these are run-time variables, not build time, which should come from the
config.mak.uname. In any event, I'm in a situation where I do not have the
security to create the actual ../etc directory so am trying to test an
alternate
location. Some of the customers I am supporting have experienced this also.

Any ideas on handling an execution time override of the system location,
instead of
just using GIT_CONFIG_NOSYSTEM to turn off --system?

I would gladly add GIT_CONFIG_SYSTEM=path with a little guidance, if that's
what it
comes down to.

--Randall


  reply	other threads:[~2025-01-29 17:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 16:34 [BUG] PREFIX environment variable ignored by git config --system rsbecker
2025-01-29 16:41 ` Junio C Hamano
2025-01-29 17:01   ` rsbecker [this message]
2025-01-29 20:15     ` Junio C Hamano
2025-01-29 20:33       ` rsbecker
2025-01-29 23:36         ` Junio C Hamano
2025-01-29 23:49           ` rsbecker
2025-01-29 23:53             ` Junio C Hamano
2025-01-30  0:07               ` rsbecker
2025-01-30  0:23                 ` Junio C Hamano
2025-01-30  0:37                   ` rsbecker
2025-01-30 19:37                     ` Ben Knoble
2025-01-30 21:57                     ` Junio C Hamano
2025-01-29 18:20   ` rsbecker
2025-01-29 23:48   ` Junio C Hamano

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='008201db726f$6e6990b0$4b3cb210$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.