#5628: [with patch; needs review] a little sage-flags.txt issue
--------------------------+-------------------------------------------------
Reporter: was | Owner: was
Type: defect | Status: new
Priority: blocker | Milestone: sage-3.4.1
Component: distribution | Keywords:
--------------------------+-------------------------------------------------
Comment(by tornaria):
The issue with this patch is that the {{{sage-flags.txt}}} file will not
be regenerated unless sage install directory changes (because
{{{write_flags_file()}}} is only called from within {{{install_moved()}}}.
Maybe the flags file should also be created from the
{{{check_processor_flags()}}} function. But then, this only works if sage
is run at least once after an upgrade.
Otherwise, doing {{{sage -upgrade}}} followed by {{{sage -bdist}}} ends up
with a sage binary with no {{{sage-flags.txt}}}, defeating the purpose of
the flags file.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5628#comment:2>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
