mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Riesch <michael.riesch@wolfvision.net>
To: ptxdist@pengutronix.de, "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: Re: [ptxdist] Globally define GIT_CEILING_DIRECTORIES?
Date: Tue, 14 Feb 2023 11:32:59 +0100	[thread overview]
Message-ID: <8ada6b60-6024-57c7-ab9c-364458129e2e@wolfvision.net> (raw)
In-Reply-To: <7a6848be-61a6-6e2b-eb1c-7f9490676f82@pengutronix.de>

Hi Sven,

On 2/13/23 14:58, 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.

We can add the libcamera project to that list. There is a script inside
libcamera that checks whether the sources are in a git tree. If yes, the
version obtained by git describe is used. As a fallback, the meson
project version is used. As a consequence, the version of our BSP is
leaked into libcamera.

I haven't tested this GIT_CEILING_DIRECTORIES approach but it seems to
me that it would do the trick.

> Given this is a global change, does anyone see a potential problem?

Can't be the judge of that, though.

Best regards,
Michael



  parent reply	other threads:[~2023-02-14 10:33 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
2023-02-13 15:03   ` Sven Püschel
2023-02-13 19:27     ` Christian Melki
2023-02-14 10:32 ` Michael Riesch [this message]
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=8ada6b60-6024-57c7-ab9c-364458129e2e@wolfvision.net \
    --to=michael.riesch@wolfvision.net \
    --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