Re: [sage-devel] Modularization project: V. The blocs

2023-06-16 Thread Matthias Koeppe
On Friday, June 16, 2023 at 12:52:16 PM UTC-7 David Roe wrote: How do you handle files that depend on multiple libraries (like both FLINT and NTL for example)? Are these only included in sagemath-standard? In many cases, such multiple dependencies are gratuitous and can be resolved by splitti

Re: [sage-devel] Modularization project: V. The blocs

2023-06-16 Thread David Roe
How do you handle files that depend on multiple libraries (like both FLINT and NTL for example)? Are these only included in sagemath-standard? David On Fri, Jun 16, 2023 at 2:19 PM Matthias Koeppe wrote: > On Friday, June 16, 2023 at 11:07:36 AM UTC-7 David Roe wrote: > > I assume that the MANI

Re: [sage-devel] Modularization project: V. The blocs

2023-06-16 Thread Matthias Koeppe
On Friday, June 16, 2023 at 11:07:36 AM UTC-7 David Roe wrote: I assume that the MANIFEST.in.m4 file contains a list of what's in each package, right? That's right, this is the current mechanism. I have plans for switching this to something more maintainable, which will also enforce that the

Re: [sage-devel] Modularization project: V. The blocs

2023-06-16 Thread David Roe
I assume that the MANIFEST.in.m4 file contains a list of what's in each package, right? There's also sagemath-objects and sagemath-categories (are there any others?); can you send analogous links for those so that we can understand how the library is being broken up into pieces? Is every file par

[sage-devel] Modularization project: V. The blocs

2023-06-16 Thread Matthias Koeppe
(index of previous posts: https://github.com/sagemath/sage/issues/29705) A common wisdom applies: *Do your combinatorial explosions at home, not in public.* In other words, we should not attempt to define a distribution package for every possible community or subfield of mathematics that Sage s