#13395: Fix upgrading with GCC
----------------------------------+-----------------------------------------
Reporter: jdemeyer | Owner: jdemeyer
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-5.4
Component: build | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Jeroen Demeyer | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by jdemeyer):
Replying to [comment:13 jhpalmieri]:
> If sage-env gets sourced more than once (as can happen during upgrading
with this patch), we will get duplicate entries in $PATH,
$LD_LIBRARY_PATH, and others.
True.
> I don't think this is an issue, but it was one of the points of #10469.
Should I be concerned about this?
Personally, I am not concerned about this. I don't see a problem (apart
from efficiency perhaps) with having duplicate `PATH` or `LD_LIBRARY_PATH`
entries. Also note that #10469 did not point out a particular problem
that this causes.
Also remember that this can happen only ''during'' upgrading.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13395#comment:17>
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.
