On Tue, Sep 9, 2025 at 10:31 PM 'tobia...@gmx.de' via sage-devel <sage-devel@googlegroups.com> 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 > relatively simple, since it's essentially only used in > src\sage\misc\sagedoc.py and there we could simply open the live website > instead of launching our own http server. > > | 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 why/how sagelib should determine where you (or > your distro) will end up installing the documentation. Say on arch, I'm > installing the sagemath-doc package which puts it in usr/share/doc/sage. How > do you communicate that to sagemath? Another distro might want put it in > another folder... We could add a config build variable for sagelib that says > "I might install your docs in this place" and then use this as the default > for SAGE_DOC. sage-the-distro can then set it to build/sage-distro, while > arch sets its to usr/share/doc/sage etc. But all of this sounds rather > complicated if you could 009open a webbrowser at https://doc.sagemath.org/ > instead. > > Scipy for example just says "Documentation is available in the docstrings and > online at https://docs.scipy.org/doc/scipy/";, and is done with this topic. > Since for at least three years they also don't build their docs as pdfs > anymore. > > | Anyway, the online doc is for version 10.6. > > We might have talked about this before: what about hosting the final docs > also on netlify (with the same github publishing infrastructure we currently > have in place for https://doc-develop--sagemath.netlify.app). In my > experience, there were no problems with this setup (apart from general issues > building the docs) and it's fully automated.
www.sagemath.org is hosted om github Pages, and this makes it quite easy to upload built docs there. So this can be automated, say, via https://github.com/JamesIves/github-pages-deploy-action (I did use it here: https://github.com/cddlib/polyhedral_faq/blob/main/.github/workflows/main.yml - just one file there, but certainly it should be able to do directories) Dima > > -- > 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 discussion visit > https://groups.google.com/d/msgid/sage-devel/1b2a078e-4104-4639-87e6-919858977dc4n%40googlegroups.com. -- 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 discussion visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq0e6tST1SaX07i2ttDKrbmAqU%3DT9qY9CDqLGi5xhxXJ7A%40mail.gmail.com.
