git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: [BUG] PREFIX environment variable ignored by git config --system
Date: Wed, 29 Jan 2025 11:34:26 -0500	[thread overview]
Message-ID: <007f01db726b$ac911ce0$05b356a0$@nexbridge.com> (raw)

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
locate
System configuration items, per 10.8 in the git-scm website documentation
on Environment Variables.
Git should have reported:
fatal: unable to read config file '/home/randall/etc/gitconfig': No such
file or directory

What happened instead? (Actual behavior)
git used /usr/local-ssl3.0/etc/gitconfig instead and reported that the file
does not exist:
fatal: unable to read config file '/usr/local-ssl3.0/etc/gitconfig': No such
file or directory

What's different between what you expected and what actually happened?
The directory being used based on the PREFIX variable.

Anything else you want to add:
This appears to be a problem on all platforms.

[System Info]
git version:
git version 2.47.1
cpu: NSV
built from commit: 92999a42db1c5f43f330e4f2bca4026b5b81576f
sizeof-long: 4

[System Info]
git version:
git version 2.45.1
cpu: x86_64
no commit associated with this build
sizeof-long: 8

--
Brief whoami: NonStop&UNIX developer since approximately
UNIX(421664400)
NonStop(211288444200000000)
-- In real life, I talk too much.




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

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 16:34 rsbecker [this message]
2025-01-29 16:41 ` [BUG] PREFIX environment variable ignored by git config --system Junio C Hamano
2025-01-29 17:01   ` rsbecker
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='007f01db726b$ac911ce0$05b356a0$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --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).