Gentoo Packages

Starting with 10.3.beta4 building the pdf documentation with the useflag doc-pdf in sage-doc uses luatex and requires at least texlive 2023. texlive 2023 is not, at the time of writing, in the main tree but developped in the texlive overlay. If you want to generate sage's pdf documentation you will have to use the texlive overlay or a manual installation of texlive https://wiki.gentoo.org/wiki/TeX_Live_manual_installation

For convenience, I have added two files in the package.keywords folder:

• texlive-2023 which has a list of package to unmask from the texlive overlay

and overlay setup instructions

• texlive-2023.license some packages needed from the overlay have new licenses

and this file details them and can be used in a package.license folder in /etc/portage or be appended to a package.license file depending on what you are using.

Note that if you do not want to build the pdf documentation, you do need to do anything. Building the default html documentation do not require anything out of the main Gentoo tree.

sage 9.5 is in its release candidate as I am writing this. Some important changes are coming to the way sage is distributed upstream and in sage-on-gentoo. Upstream is taking steps to modularise sage and I am following their lead. People who have been using this overlay for a long time will remember that sage was split in several ebuilds before being stitched together in a single one. In some way we are going back to that time. Compared to sage 9.4, sage 9.5 will be split into the following ebuilds

• sage_setup
• sage
• sage_docbuild
• sage-doc

There will probably be at least a "sage_conf" ebuild for sage-9.6. I didn't think it was mature enough to split it in 9.5.

To help manage these ebuilds a sagemath set has been created and is stored in the overlay at sets/sagemath, see http://wiki.gentoo.org/wiki//etc/portage/sets for more informations about sets. The set can be linked in similar way that keyword and use files are to become usable. There will be updated instructions for it in the overlay README.

There will be some changes to use flags as well. "doc-html", "doc-html-bin" and "doc-pdf-bin" will be removed. The sage ebuild will have a standard "doc" flag to trigger the installation of sage-doc. html documentation will be installed by default. As it turns out it is a requirement to build the pdf documentation. Binary documentation install will be triggered by a new "prebuild" flag.

Note for people brave enough to build the documentation in html and pdf in all available languages: There is a race condition in make that manifest itself when building html and pdf for many languages. It became apparent when we fixed parallel make for the documentation. Building with a few less threads usually works.

Gap-4.10.1 is ready and unfortunately upgrading is still painful. I am hopeful that these pains will finally ease in future release.

If on upgrading gap (as a sage dependency or stand alone) gap-4.10.1 is not offered because of conflicting dependencies the quickest way to resolve the conflict is to uninstall gap and all the gap packages before re-installing again.

The following commands will un-install gap and all the gap packages from your system

emerge -C gap emerge -C `equery -q l -F '$category/$name' dev-gap/*`

If you want to preserve your list of gap packages for quick re-install after upgrading run

equery -q l -F '$category/$name' dev-gap/* > gap_pkg.txt

prior to un-install. You can then use the saved file to re-install your old list of gap packages.

emerge -v `cat gap_pkg.txt`