On Tue, Sep 9, 2025 at 9:47 AM 'tobia...@gmx.de' via sage-devel
wrote:
>
>
> As of 10.8.beta2 (perhaps also earlier releases), the built documentation is
> found in build/sage-distro/src/doc/html/en/reference. The standard location
> was local/share/doc/sage/html/en/reference.
>
> Is this intend
On Thursday, September 11, 2025 at 10:02:48 AM UTC+8 François Bissey wrote:
These days, I set it at build time in the file that becomes: sage/config.py
which defines all those things that are different in gentoo compared to
some other environments.
Hopefully, we can improve the meson setup a
On Wednesday, September 10, 2025 at 12:17:27 PM UTC+8 Kwankyu Lee wrote:
We really should just remove all those SAGE_xyz variables.
Why? Do you assume that sage-the-distro is dead?
I do think it's close to dead, but that's not the point. The reason why
SAGE_xyz should not be used is bec
https://github.com/sagemath/sage/pull/40807 needs review.
--
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 sage-devel+unsubscr...@googlegroups.com.
To view this dis
...
SAGE_SHARE: Also doesn't make sense outside of sage-the-distro. Instead of
looking for stuff there at runtime, you should try to find your resources
at build time.
They all make sense in sage-the-distro.
... so you have to set SAGE_DOC after you build the docs to tell sagelib
where
On 10/09/2025 20:51, 'tobia...@gmx.de' via sage-devel wrote:
meson setup build
meson compile -C build doc-html
cp -r build/src/doc/html usr/share/doc/sage-$VERSION
As for example done on arch:
https://github.com/gripped/archpkgbuilds/blob/master/extra/sagemath-doc/PKGBUILD
How do you currentl
On Wed, Sep 10, 2025 at 4:28 AM Kwankyu Lee wrote:
>
> ...
> SAGE_SHARE: Also doesn't make sense outside of sage-the-distro. Instead of
> looking for stuff there at runtime, you should try to find your resources at
> build time.
>
>
> They all make sense in sage-the-distro.
>
>
> ... so you hav
On 2025-09-10 16:30:09, François Bissey wrote:
> Even if sage-the-distro was dead, those variables are useful.
> And if we say it is dead, well, it should go in a more standard
> location, which at minimum would be $prefix/share/doc and configurable.
> In Gentoo we want stuff in /usr/share/doc/pk
On Tue, Sep 9, 2025 at 10:31 PM 'tobia...@gmx.de' via sage-devel
wrote:
>
> +export SAGE_DOC="$SAGE_ROOT/build/sage-distro/src/doc"
>
>
> This fixes it only for sage-the-distro, not for anyone else. We really should
> just remove all those SAGE_xyz variables. For SAGE_DOC this should be
> relati
On 10/09/2025 16:17, Kwankyu Lee wrote:
We really should just remove all those SAGE_xyz variables.
Why? Do you assume that sage-the-distro is dead?
Even if sage-the-distro was dead, those variables are useful.
And if we say it is dead, well, it should go in a more standard
location,
We really should just remove all those SAGE_xyz variables.
Why? Do you assume that sage-the-distro is dead?
| doc is built after sage is built. Why not just put SAGE_DOC under '-o'?
It's already falling back to SAGE_DOC if you don't specify '-o'. But that
doesn't solve the question wh
+export SAGE_DOC="$SAGE_ROOT/build/sage-distro/src/doc"
This fixes it only for sage-the-distro, not for anyone else. We really
should just remove all those SAGE_xyz variables. For SAGE_DOC this should
be relatively simple, since it's essentially only used
in src\sage\misc\sagedoc.py and the
On Tue, Sep 9, 2025 at 6:27 PM Kwankyu Lee wrote:
>
>
>
> On Tuesday, September 9, 2025 at 11:47:50 PM UTC+9 tobia...@gmx.de wrote:
>
> In the case of `reference`, is there a good reason this is not simply
> opening https://doc.sagemath.org/ in case SAGE_DOC doesn't point to an
> existing folde
On Tuesday, September 9, 2025 at 11:47:50 PM UTC+9 tobia...@gmx.de wrote:
In the case of `reference`, is there a good reason this is not simply
opening https://doc.sagemath.org/ in case SAGE_DOC doesn't point to an
existing folder?
SAGE_DOC should point to an existing folder if doc was buil
The docs are placed in whatever folder you pass under `-o` to the
sage_docbuild script. In the case of `make doc-html` this is indeed some
folder under build/sage-distro, but it could be also a completely different
directory.
doc is built after sage is built. Why not just put SAGE_DOC unde
As of 10.8.beta2 (perhaps also earlier releases), the built documentation
is found in build/sage-distro/src/doc/html/en/reference. The standard
location was local/share/doc/sage/html/en/reference.
Is this intended or a bug?
The docs are placed in whatever folder you pass under `-o` to the
s
On Tuesday, September 9, 2025 at 9:58:57 AM UTC+9 Kwankyu Lee wrote:
... in src/sage/misc/sagedoc.py. But as you see, the "not tested" tag makes
it useless. Why a doctest is "not tested"?
To prevent undesirable side effects, such as opening an web browser.
OK.
--
You received this messa
17 matches
Mail list logo
