Changes between Initial Version and Version 1 of Ticket #18748, comment 25


Ignore:
Timestamp:
06/25/15 10:06:32 (4 years ago)
Author:
jdemeyer
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18748, comment 25

    initial v1  
    11Replying to [comment:23 vbraun]:
    22> You didn't complain about `sage-download-file` 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 `sage-spkg` 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`.
     3We 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 `sage-spkg` 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`.
    44
    55I always found it awkward that we have a top-level `Makefile` calling a scipt `build/install` running make on `build/Makefile` which then runs `src/bin/sage-spkg` which in turn runs `build/pkgs/*/spkg-install`. That's a mess. This ticket creates an opportunity to start cleaning this up, let's do it right from the beginning.