On Monday, December 30, 2019 at 9:57:25 PM UTC-8, Isuru Fernando wrote:
>
> I'm trying to build sage 9.0.rc1 for conda. For conda what I do is I run,
> 1. Run configure
> 2. cp src/bin/* to <prefix>/bin
> 3. cp src/ext/* to <prefix>/share/sage/ext
> 4. run `python setup.py install` in src
>
> This has worked fine until 8.9
>
> In 9.0 some scripts in `src/bin/` use `sage-system-python` which is in
> `build/bin/`. Shouldn't scripts like `sage-system-python` be used only in
> scripts under `build`?
>
> Isuru
>
These scripts use sage-system-python:
sage-coverage
sage-coverageall
sage-location
sage-num-threads.py
sage-pkg
sage-pypkg-location
sage-unzip
Most of these are for development work and/or with package maintenance (for
example sage-pkg or sage-unzip), and since they are also used in various
command line options ("./sage -pkg ..."), they should be in src/bin. Also,
scripts which are supposed to run even if Sage has not been built should
use sage-system-python, and some of these fit into that category (e.g. the
packaging scripts, sage-coverage, maybe sage-num-threads). Which scripts
are causing problems for you?
--
John
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/2cf9b9fe-1ba9-48e5-a95b-a5ddc7cc53a8%40googlegroups.com.
