#14346: The pari spkg is patching upstream too heavily
--------------------------------------+-------------------------------------
       Reporter:  Snark               |         Owner:  tbd          
           Type:  enhancement         |        Status:  new          
       Priority:  major               |     Milestone:  sage-wishlist
      Component:  packages: standard  |    Resolution:               
       Keywords:                      |   Work issues:               
Report Upstream:  N/A                 |     Reviewers:               
        Authors:                      |     Merged in:               
   Dependencies:                      |      Stopgaps:               
--------------------------------------+-------------------------------------

Comment (by fbissey):

 Replying to [comment:8 jdemeyer]:
 > Replying to [comment:6 Snark]:
 > > The commits used were from upstream, but the patch is '''based''' on
 those commits -- it's not just them. That means that the pari in sage is
 neither compatible with upstream's 2.5.3, nor with the upcoming 2.6.0.
 > I thought backporting patches from later upstream versions is standard
 practice.

 I'll have a shot at that one but it's probably nothing new to you. It
 depends on the trade off. Backporting in a distro like debian that is
 keeping fixed version of the software has much as possible is good.... so
 long as you preserve API. If the patch breaks API that means potentially
 all dependencies will need patching for the new API. So the trade off is
 between the number of dependencies you have to patch for the new API and
 how badly you want/need the backport.

 It applies also to sage but the scale is a priori less than in a full
 distro. In the case of pari in particular, I don't think the list of
 dependencies (especially dependencies not in sage) affected by your change
 is very long (make that non existant until proven otherwise).

 Debian my have enshrined the above discussion in a precise policy but I am
 not a deban-er.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14346#comment:10>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to