git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: git@vger.kernel.org
Cc: Steffen Nurpmeso <steffen@sdaoden.eu>
Subject: meson build: datadir missing?
Date: Mon, 03 Mar 2025 21:33:20 +0100	[thread overview]
Message-ID: <20250303203320.lP10PHC5@steffen%sdaoden.eu> (raw)

Hello again after a long time.

I opened

  https://git.crux.nu/ports/opt/issues/18

at my linux distro ([ports/opt] git: creates incomplete repos),
because hook etc directories were missing:

  warning: templates not found in /share/git-core/templates

He then said

  Try setting

    [init]
      templatedir = /usr/share/git-core/templates

  in your gitconfig.

which made me wonder since that is the default, so i looked and
saw his change to switch to meson back in January.  (What a pity,
i liked the make system; only that it requires GNU make, but
well..).  I then said (it is a web ui, sorry):

  hi. thanks, i see now (after looking around). it is a fallout of switching to meson, that build system seems incomplete

  master:meson.build: '-DDEFAULT_GIT_TEMPLATE_DIR="' + get_option('datadir') / 'git-core/templates' + '"',

  but that "datadir" does not happen to be set at all it seems; is this known upstream? (Hamano does not like me either, so i will not do that..)

  Only wondering why this happens at all, and is not covered by its tests, really.

  Ok i overwrite the default with the real default in my config, thanks again.


While here, since a couple of months maybe i get a problem on my
spare notebook when i sync the filesystem (btrfs).
To reproduce:

  #?0|kent:~# mount /media/btrfs-master/
  #?0|kent:/media/btrfs-master# cd crux/kent/root
  #?0|kent:/media/btrfs-master/crux/kent/root# chroot .

^(we are now chroot(1)ed to the same what is /, actually.)

  #?0|kent:/# cd root/
  #?0|kent:~# git co kent
  git: ../git-2.48.1/exec-cmd.c:50: system_prefix: Assertion `executable_dirname' failed.
  Aborted

It will work if i do /usr/bin/git, effectively the same binary.
However, this does not apply "normally":

  #?0|kent:~# cd /
  #?0|kent:/# chroot .
  #?0|kent:/# cd root
  #?0|kent:~# git co kent
  M       hosts/iwd.network/.known_network.freq
  Switched to branch 'kent'
  #?0|kent:~# git co master
  M       hosts/iwd.network/.known_network.freq
  Switched to branch 'master'

Whatever the actual logic is, it seems a bit odd, and furthermore,
and most of all, the above assertion is not a real help to solve
the problem at hand, some kind of hint to a solution would be
tremendous!

Thanks for git, and ciao!

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

             reply	other threads:[~2025-03-03 20:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 20:33 Steffen Nurpmeso [this message]
2025-03-04  7:08 ` meson build: datadir missing? Patrick Steinhardt
2025-03-04 18:16   ` Steffen Nurpmeso
2025-03-05  7:19     ` Patrick Steinhardt

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=20250303203320.lP10PHC5@steffen%sdaoden.eu \
    --to=steffen@sdaoden.eu \
    --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).