what is in SAGE_ROOT/pkgs/sagemath-standard ?

32 views
Skip to first unread message

Thierry

unread,
Oct 14, 2021, 3:28:22 PM10/14/21
to sage-devel
Hi,

a new SAGE_ROOT/pkg/ appeared, and contains sagemath-standard/build/
which weights 3,2G and contains 4 directories:

cythonized/
lib.linux-x86_64-3.9/
scripts-3.9/
temp.linux-x86_64-3.9/

What is the purpose of those directory ? Which could be removed without
breaking Sage runtime ? Which could be removed without taking some time
when re-running make build ?

Ciao,
Thierry

Matthias Koeppe

unread,
Oct 14, 2021, 5:02:45 PM10/14/21
to sage-devel

Thierry

unread,
Oct 14, 2021, 5:19:00 PM10/14/21
to sage-...@googlegroups.com
On Thu, Oct 14, 2021 at 02:02:45PM -0700, Matthias Koeppe wrote:
> See https://wiki.sagemath.org/ReleaseTours/sage-9.4#New_location_for_distribution_package_sources:_SAGE_ROOT.2Fpkgs

Thanks for the pointer.

Unfortunately, it does not mention the sagemath-standard/build/ and its
4 subdirectories.

Ciao,
Thierry




> On Thursday, October 14, 2021 at 12:28:22 PM UTC-7 Thierry
> (sage-googlesucks@xxx) wrote:
>
> > Hi,
> >
> > a new SAGE_ROOT/pkg/ appeared, and contains sagemath-standard/build/
> > which weights 3,2G and contains 4 directories:
> >
> > cythonized/
> > lib.linux-x86_64-3.9/
> > scripts-3.9/
> > temp.linux-x86_64-3.9/
> >
> > What is the purpose of those directory ? Which could be removed without
> > breaking Sage runtime ? Which could be removed without taking some time
> > when re-running make build ?
> >
> > Ciao,
> > Thierry
> >
> >
>
> --
> 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+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/12163af6-3e26-4612-b8ef-5a1f6cbb0ac2n%40googlegroups.com.

Matthias Koeppe

unread,
Oct 14, 2021, 6:32:18 PM10/14/21
to sage-devel
The subdirectory build is not used during runtime. Everything that is need during the runtime is in the configured prefix (default: local) or in the configured venv.
Reply all
Reply to author
Forward
0 new messages