Just a precision. Using bin-html or html means that LINGUAS=“en” must be set. The mean reason for that is two fold. 1) if LINGUAS is not set at all, no html documentation would be installed 2) the “en” language is the reference documentation and the only one to be complete. No other language has a translation of the reference documentation. Only some tutorials and/or “tour of sage”.
And also one of main point of getting the html documentation is to make it available in the sage-notebook and because only the English version has the complete reference I won’t work on getting the notebook to default to another language. Francois > On 27/07/2015, at 14:01, François Bissey <[email protected]> wrote: > > And sage-on-gentoo has undergone a substantial change > during the development phase.... > > So what is different: > this is a monolithic ebuild, in the past we had split sage > in various components, the scripts, the sage-clib sage and > the documentation. Over the last year or two only the > separation of sage-clib was strictly necessary. > > sage-clib being gone upstream we had an opportunity to house > everything under one roof. The separation was always > arbitrary as there is not much you can do with the scripts > without sage itself. Possibly you could have used sage from > python without needing the scripts (strictly speaking a couple > of files would probably need to be moved from one ebuild to > the other for it to work 100%). > > The only things that are still separate are things that are > split in a different package upstream, sage-data packages. > Most of them cannot be used without sage and at least one is > needed for sage to start. > > So when you move to sage-6.8 the following ebuilds will need > to go: > sage-baselayout > sage-clib > sage-doc or sage-doc-bin > > Special notes: > * ntl 9.3.0: this version of sage moves to the latest version > of ntl. It is probably a good idea to rebuild the packages > depending on ntl (flint, singular, libsingular, eclib). Automatic > rebuild of some of them could have been triggered but I forgot to > add the subslot to the ntl ebuild that would have allowed that to > happen before it was pushed to the main tree by Thomas Kahle. > > * x86 users will need to do some extra keywording for sage and > sci-mathematics/rw. sci-mathematics/rw was kindly added to > the tree by Michael Orlitzky but it was only added with ~amd64 > keyword. I know there are x86 users out there > (https://github.com/cschwan/sage-on-gentoo/issues/352), so you can request > the keyword > to be added the normal way in bugzilla. Once it is done, I'll keyword > sage ~x86 again (and repoman will let me do it). > > - Yes, I know - those two problems would be easily solved if I > was a full blown Gentoo-dev. > > * ~arch users. The recommended useflags for documentation are > "+bin-html -html -pdf". In the past we have encouraged people to > use sage-doc-bin rather than sage-doc. These flags reproduce > that particular set up. ~arch user in particular should adopt these > because the documentation will not build with sphinx 1.3. > There is a sage ticket to move to sphinx 1.3 but it is not ready > for inclusion yet. > > * numpy 1.9 can be used to build sage but it causes doctest failures > and some behavior are not as expected, be cautious that things can happen if > your are using numpy 1.9. It is merely allowed so it doesn't > block other packages wanting numpy 1.9 while I am working with upstreams > (both sage and numpy) to solve the various problems. > > Happy upgrading. > > Francois Bissey >
