Thanks. I've always kind of hated this construction/obfuscation of script names, because it makes it harder to find out where and how they are used. But presumably it has its uses.
On Wednesday, February 23, 2022 at 6:17:21 PM UTC-8 Matthias Koeppe wrote: > On Wednesday, February 23, 2022 at 2:21:08 PM UTC-8 John H Palmieri wrote: > >> I have questions about some of the scripts in src/bin: >> > >> - sage-native-execute: looks like a no-op. Delete? >> - sage-open — used in OS X; can we just use "open"? >> >> Yes on both of these. They have not been needed since Sage stopped > setting LD_LIBRARY_PATH (or its defunct equivalent on macOS). > >> >> - sage-rebase* — used on Cygwin only: move to build/bin? >> >> On Cygwin, users also may need to run this after using "sage -pip install > ...", so I'd suggest to keep it in src/bin > >> >> - sage-venv-config — where is this used? `git grep sage-venv-config` >> doesn't reveal much. >> >> "git grep venv-config" reveals that it is called by the installed sage > script. (The name of the script is constructed from $0.) > Its only function at the moment is to determine SAGE_VENV, which is then > used by sage-env. > > > -- 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/1df7aeea-940b-4b77-b5f7-b569b673c141n%40googlegroups.com.
