Changes between Initial Version and Version 1 of Ticket #18748, comment 25
 Timestamp:
 06/25/15 10:06:32 (4 years ago)
Legend:
 Unmodified
 Added
 Removed
 Modified

Ticket #18748, comment 25
initial v1 1 1 Replying to [comment:23 vbraun]: 2 2 > You didn't complain about `sagedownloadfile` being in `src/bin/`, so why complain now? 3 We currently have only 1 place to put scripts and that's in `$SAGE_ROOT/src/bin`. You're creating a second place, so it makes to think what is the best location. After this ticket is merged, we should move more scripts to `sage_bootstrap/bin`, in particular `sagespkg` and maybe even `$SAGE_ROOT/build/install` and `$SAGE_ROOT/build/pipestatus`. If `sage_bootstrap` would be in `$SAGE_ROOT/build`, that would lead to a clean separation of the complete build system for packages in `$SAGE_ROOT/build`.3 We currently have only 1 place to put scripts and that's in `$SAGE_ROOT/src/bin`. You're creating a second place, so it makes sense to think what is the best location. After this ticket is merged, we should move more scripts to `sage_bootstrap/bin`, in particular `sagespkg` and maybe even `$SAGE_ROOT/build/install` and `$SAGE_ROOT/build/pipestatus`. If `sage_bootstrap` would be in `$SAGE_ROOT/build`, that would lead to a clean separation of the complete build system for packages in `$SAGE_ROOT/build`. 4 4 5 5 I always found it awkward that we have a toplevel `Makefile` calling a scipt `build/install` running make on `build/Makefile` which then runs `src/bin/sagespkg` which in turn runs `build/pkgs/*/spkginstall`. That's a mess. This ticket creates an opportunity to start cleaning this up, let's do it right from the beginning.