On Jan 7, 1:26 pm, "Dr. David Kirkby" <david.kir...@onetel.net> wrote: > > In the new version of sage-env, there are two "if" statements > > involving "$SAGE_PRINT_ENVIRONMENT". It makes a lot of sense not to > > print these by default (for example, when starting Sage), but maybe > > the second group of statements, summarizing the settings of the > > variables, should be printed at the start of the "make" process. It > > seems like that could help in debugging, and since the make produces > > such a long install.log file anyway, adding a few lines doesn't seem > > like a big deal to me.
> In principle I agree with you. In practice, I'm not sure the best way to > handle it. It shouldn't hurt executing sage-env twice, right? You could make it part of the build process to invoke sage-env with $SAGE_PRINT_ENVIRONMENT set at some point, to get the variables printed. Or perhaps just print the environment at the start of the build script.
-- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
