On Fri, Aug 8, 2025 at 12:10 PM Dima Pasechnik <[email protected]> wrote:

> On Fri, Aug 8, 2025 at 11:56 AM Marc Culler <[email protected]> wrote:
> >
> > On Fri, Aug 8, 2025 at 11:50 AM Dima Pasechnik <[email protected]>
> wrote:
> >
> >> the spkgs bliss, coxeter3, meataxe, sirocco, and tdlib are tested.
> >
> >
> > I guess it depends on what you mean by "tested".  Those packages depend
> on sage_environment.
>
> They don't - you are mixing up the listed above spkgs with their
> sagemath_*-wrappers.
> E.g.
>
> $ cat build/pkgs/sirocco/dependencies
> mpfr
>
>
What I have been doing is to use options like  "--enable-sirocco" when I
run configure. I have been using those options for as many optional
packages as possible. You seem to be saying that those
options force installation of a "wrapper" which depends on
sage_environment.  So what am I supposed to do instead of using the
--enable-X option if I want to build and install an optional package X
without installing its "wrapper"?  (And what is the functional difference
between having a "wrapper" and not having one?)

- Marc

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" 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-release/CALcZXREb2_skMsn0LbTi3mxWKO8g02yRf5_s%2BCeMj1Q-OpQc2g%40mail.gmail.com.

Reply via email to