#9530: Improve/fix readline workarounds for Arch Linux and openSuSE
------------------------+---------------------------------------------------
   Reporter:  baechler  |       Owner:  GeorgSWeber             
       Type:  defect    |      Status:  needs_review            
   Priority:  major     |   Milestone:  sage-4.6                
  Component:  build     |    Keywords:  Arch Linux SuSE readline
     Author:            |    Upstream:  N/A                     
   Reviewer:            |      Merged:                          
Work_issues:            |  
------------------------+---------------------------------------------------

Comment(by TheBlackCat):

 Replying to [comment:13 drkirkby]:
 > > Yes, that is the problem.  As it stand now, Sage 4.6 will be released
 without being able to build as-is on a major distribution and won't build
 reliably on another.  We have a small, simple, low-risk fix available
 right now.  I think it would be good to incorporate the fix now rather
 than pushing it back again.

 > I've never managed to get any agreement on what is "supported". But it
 we believe README.txt, both !ArchLinux and !OpenSUSE are supported.
 However, in my opinion we should not hold a release of Sage just because
 on Linux distro has bought at yet another backwards incompatible version.
 But if a change in Sage has broken one of these systems, then I think it
 should be addressed in 4.6. But if the breakages are caused by updated
 versions of Linux, then I think these systems will just have to accept
 that.

 I agree we should not hold a release because of the lack of a fix for a
 new break caused by the distribution. However, neither is the case here.

 The breakage first appeared in openSUSE 11.2, which was released almost a
 year ago.  openSUSE 11.3, which also has the problem, was released over 3
 months ago.  So it is a long-standing issue.

 Further, a fix is available, and has been for over 3 months now (shortly
 after openSUSE 11.3 was released).  The fix was published several weeks
 before sage 4.5.2 was released, over a month and a half before 4.5.3.

 So this is a long-standing issue for which a fix has been available for a
 while.  Given that, I do not think holding 4.6 until the existing fix has
 been incorporated is outlandish.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9530#comment:15>
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.

Reply via email to