Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-14 Thread Matthias Koeppe
On Thursday, March 11, 2021 at 3:23:03 PM UTC-8 François Bissey wrote: > > On 12/03/2021, at 12:14, Matthias Koeppe wrote: > > this one? https://pypi.org/project/sagemath-standard/#files > > Even for betas? I was thinking there would only be some for proper > releases. > Yes, pip handles thi

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-12 Thread Matthias Koeppe
On Friday, March 12, 2021 at 2:38:31 AM UTC-8 erik@gmail.com wrote: > You can also run `./setup.py develop` to have all extension modules > copied into the main package source, so that it can be directly > importable. > Good news: The next beta of Sage will support this - see https://trac

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-12 Thread E. Madison Bray
On Thu, Mar 11, 2021 at 5:18 AM Nathan Dunfield wrote: > > > > On Wednesday, March 10, 2021 at 4:50:41 AM UTC-6 Dima wrote: >> >> numpy does this: >> https://numpy.org/devdocs/docs/howto_build_docs.html >> >> you can only build numpy docs after numpy is installed. > > > Of course, with numpy "inst

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-11 Thread François Bissey
> On 12/03/2021, at 12:14, Matthias Koeppe wrote: > > On Thursday, March 11, 2021 at 3:07:41 PM UTC-8 François Bissey wrote: > > > On 12/03/2021, at 11:48, Matthias Koeppe wrote: > When are we going to start seeing separate sdist tarballs? That’s really the > point at which > I am going t

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-11 Thread Matthias Koeppe
On Thursday, March 11, 2021 at 3:07:41 PM UTC-8 François Bissey wrote: > > > On 12/03/2021, at 11:48, Matthias Koeppe wrote: > When are we going to start seeing separate sdist tarballs? That’s really > the point at which > I am going to switch the way I do things. this one? https://pypi.org/

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-11 Thread François Bissey
> On 12/03/2021, at 11:48, Matthias Koeppe wrote: > > No, there's nothing wrong with it; this is the normal way to use the > repository now and in the planned future. > After running ./bootstrap, the source tree contains several self-contained > Python distribution package source trees in b

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-11 Thread François Bissey
> On 12/03/2021, at 11:20, Matthias Koeppe wrote: > > Well, autotools does not even have a mechanism to advertise > dependencies/requirements -- other than "configure" exiting with an error if > they are not satisfied. You as a downstream package maintainer declare and > update the requirem

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-11 Thread Matthias Koeppe
On Thursday, March 11, 2021 at 2:33:18 PM UTC-8 François Bissey wrote: > I guess it is my fault for doing CI, including doc, straight from git. > No, there's nothing wrong with it; this is the normal way to use the repository now and in the planned future. After running ./bootstrap, the source

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-11 Thread François Bissey
> On 12/03/2021, at 11:20, Matthias Koeppe wrote: > > And then -- of course likely not relevant for gentoo -- there is also the > distinction between source and binary distributions (wheels): For the package > itself, many users have a good reason to build it from source; but for a > separa

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-11 Thread Matthias Koeppe
On Thursday, March 11, 2021 at 1:28:12 PM UTC-8 François Bissey wrote: > > On 12/03/2021, at 09:46, Matthias Koeppe wrote: > > you get this type of build isolation for free if you make the > documentation a separate distribution according to PEP 517 > (pyproject.toml), for which you declare t

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-11 Thread François Bissey
> On 12/03/2021, at 09:46, Matthias Koeppe wrote: > > On Wednesday, March 10, 2021 at 8:18:11 PM UTC-8 Nathan Dunfield wrote: > On Wednesday, March 10, 2021 at 4:50:41 AM UTC-6 Dima wrote: > numpy does this: > https://numpy.org/devdocs/docs/howto_build_docs.html > > you can only build numpy d

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-11 Thread François Bissey
> On 12/03/2021, at 09:41, Matthias Koeppe wrote: > > On Thursday, March 11, 2021 at 11:36:18 AM UTC-8 Antonio Rojas wrote: > Here is my current PKGBUILD (after some cleanup I did today) > https://github.com/archlinux/svntogit-community/blob/packages/sagemath-doc/trunk/PKGBUILD > I'm building

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-11 Thread Matthias Koeppe
On Wednesday, March 10, 2021 at 8:18:11 PM UTC-8 Nathan Dunfield wrote: > On Wednesday, March 10, 2021 at 4:50:41 AM UTC-6 Dima wrote: > >> numpy does this: >> https://numpy.org/devdocs/docs/howto_build_docs.html >> >> you can only build numpy docs after numpy is installed. >> > > Of course, with

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-11 Thread Matthias Koeppe
On Thursday, March 11, 2021 at 11:36:18 AM UTC-8 Antonio Rojas wrote: > Here is my current PKGBUILD (after some cleanup I did today) > https://github.com/archlinux/svntogit-community/blob/packages/sagemath-doc/trunk/PKGBUILD > I'm building the docs in a separate package for practical purposes (sa

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-11 Thread Antonio Rojas
El miércoles, 10 de marzo de 2021 a las 21:13:15 UTC+1, François Bissey escribió: > I’d like to talk to you on another channel, I have to do a small > patch currently. It may reflect different packaging strategy or > something I could improve. > Here is my current PKGBUILD (after some cleanup

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-10 Thread Nathan Dunfield
On Wednesday, March 10, 2021 at 4:50:41 AM UTC-6 Dima wrote: > numpy does this: > https://numpy.org/devdocs/docs/howto_build_docs.html > > you can only build numpy docs after numpy is installed. > Of course, with numpy "installed" doesn't necessarily mean installed in the main site-packages, y

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-10 Thread François Bissey
> On 11/03/2021, at 05:03, Matthias Koeppe wrote: > > On Wednesday, March 10, 2021 at 1:21:07 AM UTC-8 François Bissey wrote: > [...] building the documentation [...] > > In https://trac.sagemath.org/ticket/29868 I sketch a design that is in line > with modern Python packaging, in particula

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-10 Thread François Bissey
> On 11/03/2021, at 01:10, Antonio Rojas wrote: > > El miércoles, 10 de marzo de 2021 a las 10:21:07 UTC+1, François Bissey > escribió: > Instead of trying to fix the problem that you should be building the > documentation > before installing, the push to modularisation is currently used to

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-10 Thread François Bissey
> On 10/03/2021, at 23:50, Dima Pasechnik wrote: > > On Wed, 10 Mar 2021, 09:21 François Bissey, wrote: > So the situation is now: > * install package A > * install package B > * make a package C that takes B and applies it to the install of A and install > the documentation of A (not C). >

Re: [sage-devel] distro packaging, docbuilding and modularisation

2021-03-10 Thread Dima Pasechnik
On Wed, 10 Mar 2021, 09:21 François Bissey, wrote: > Hi all, > > So today I will be talking about subject that I in sage-on-gentoo have > brushed under the carpet for years focusing on helping to be able to > use more and more components of the system and ultimately get “sagelib” > to be one such

[sage-devel] distro packaging, docbuilding and modularisation

2021-03-10 Thread François Bissey
Hi all, So today I will be talking about subject that I in sage-on-gentoo have brushed under the carpet for years focusing on helping to be able to use more and more components of the system and ultimately get “sagelib” to be one such component. Sagemath as a meta distribution of stuff has bad ha