#10491: Dump environment before building
-----------------------------+----------------------------------------------
Reporter: jdemeyer | Owner: GeorgSWeber
Type: enhancement | Status: closed
Priority: minor | Milestone: sage-4.6.1
Component: scripts | Resolution: fixed
Keywords: scripts install | Author: Jeroen Demeyer
Upstream: N/A | Reviewer: Volker Braun
Merged: sage-4.6.1.rc0 | Work_issues: Don't always dump the
environment.
-----------------------------+----------------------------------------------
Changes (by jdemeyer):
* work_issues: Don't always dump the whole environment. => Don't always
dump the environment.
Comment:
Replying to [comment:5 leif]:
> It's totally odd to dump the whole environment whenever `make something`
is run, where `something` includes `doc`, `ptestlong` and most of all
other targets.
Agreed.
> I would
> * make the output depend on some environment variable (''not''
`SAGE_DEBUG` ;-) , but perhaps `SAGE_DEBUG_BUILD` to be also used
elsewhere),
Makes sense.
> * limit the output to "relevant" variables; I e.g. personally use
Disagree, you never know in advance which environment variables are
"relevant". If a build fails, it might be because of some obscure
environment variable. That's why I added this patch.
> * use `printenv`, the shell built-in, instead of `env`.
Disagree, {{{env}}} is more portable than {{{printenv}}}.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10491#comment:9>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
