mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Christian Melki <christian.melki@t2data.com>
To: s.pueschel@pengutronix.de
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Globally define GIT_CEILING_DIRECTORIES?
Date: Mon, 13 Feb 2023 15:24:25 +0100	[thread overview]
Message-ID: <4aceca32-4f80-a657-f375-b0bcf8b3c16e@t2data.com> (raw)
In-Reply-To: <7a6848be-61a6-6e2b-eb1c-7f9490676f82@pengutronix.de>

Hi Sven.

On 2/13/23 2:58 PM, Sven Püschel wrote:
> I would suggest globally setting the GIT_CEILING_DIRECTORIES environment variable when building packages.
> 
> Besides lshw, sockperf is now the second time I've encountered the buildsystem to check the current git repository. But as Git also checks the parent directories when searching for Git repositories, these checks may result in getting an unwanted Git repository (usually the BSP), resulting in package versions with a Git commit/version that has nothing to do with the actual package.
> 
> With GIT_CEILING_DIRECTORIES set to the parent directory of the extracted sources, Git will stop searching for parent Git repositories, when it encounters this directory. See my sockperf v2 patch for an example of using this environment variable.
> 
> Given this is a global change, does anyone see a potential problem?
> 
> 
> Best regards
> 
> Sven
> 
> 

Just to summarize so I understand this.
You want to limit the searching for git repos,
so that if it isn't found in the current posix PWD (cwd), it's not a git repo?
I'm assuming it's expandable by doing an export to $PWD?

Have you tried this as an global?
Afaict, sockperf treats this locally?

Also, do you have any anecdotal or factual history from other build environments?
Some of them rely extensively on git hashes, ie, repos.
They've likely stumbled upon the same question.

Regards,
Christian



  reply	other threads:[~2023-02-13 14:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 13:58 Sven Püschel
2023-02-13 14:24 ` Christian Melki [this message]
2023-02-13 15:03   ` Sven Püschel
2023-02-13 19:27     ` Christian Melki
2023-02-14 10:32 ` Michael Riesch
2023-02-14 14:21 ` Michael Olbrich
2023-02-27 21:22   ` Michael Riesch
2023-03-03  7:25     ` Michael Olbrich
2023-03-06  8:34       ` Michael Riesch

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=4aceca32-4f80-a657-f375-b0bcf8b3c16e@t2data.com \
    --to=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.de \
    --cc=s.pueschel@pengutronix.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