On Sun, Apr 21, 2013 at 12:17:33PM +0200, Felix Salfelder wrote:
> 1 write/exchange the build systems for the core parts (c_lib,
> python-sage, extcode...).
> 2 modify sage ("the distribution") to use the new build systems instead
> of running 'setup.py'.
> 3 build stand-alone sage, draft debian packages, figure out dependencies
I must add sage-scripts (currently the directory <git-transition-repo>/src/bin)
to (1). it seems to be more work.
my approach would be to use a configure script to find other programs and then
-- before installation -- replace things like
grep -i version "$SAGE_LOCAL/bin/sage-banner"
by
grep -i version "@sage-banner@"
and
if [ "$1" = '-gap' -o "$1" = '--gap' ]; then
shift
exec "$SAGE_LOCAL/bin/gap" "$@"
fi
by
if [ "$1" = '-gap' -o "$1" = '--gap' ]; then
shift
exec "@gap@" "$@"
fi
then within an ordinary distribution one could simply set
@sage-banner@ to sage-banner and @gap@ to gap.
when installing for sage ("the distribution"), the configure script can
substitute @sage-banner@ for $SAGE_LOCAL/bin/sage-banner and choose
@gap@ to be either $SAGE_LOCAL/bin/gap or "/whatever/prefix/for/gap", depending
on where gap can be found.
(any problems with this? better ideas?)
but i'm curious: why doesn't sage simply use $PATH to locate executables? this
looks quite involved, what's the point?
regards
felix
--
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
