On 2026-03-03 12:08:25, Marc Culler wrote:
> So the "belt and suspenders" solution to this problem is to use both -E and
> Print in both meson.build and gap/spkg-configure.m4.

At the risk of this becoming a theme, Tobias started working on a PR that
would minimize these shenanigans:

  https://github.com/tobiasdiez/sage/pull/19

The summary is that we can find the main GAP root on-the-fly by either

  1. gap --print-gaproot (very official sounding)
  2. pkg-config --variable=libdir libgap (also works, and is faster)
  3. Doing either of those at build time, and putting the value
     in GAP_ROOT_PATHS like we do now

In all three cases, we would need to append $HOME/.gap to the
list. (The existing trick prints $HOME/.gap, those above do not.)

Except for one corner case that we could quietly un-support, the list
of paths is only needed at startup, to search for GAP files that may
have changed and (if so) would invalidate your cached workspace.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/sage-devel/aacoxJxHkFn0g-iT%40mertle.

Reply via email to