#8059: update Singular SPKG to newest upstream release
-------------------------------+--------------------------------------------
   Reporter:  malb             |       Owner:                                   
         
       Type:  enhancement      |      Status:  needs_work                       
         
   Priority:  major            |   Milestone:  sage-4.5                         
         
  Component:  packages         |    Keywords:                                   
         
     Author:  Martin Albrecht  |    Upstream:  Fixed upstream, in a later 
stable release.
   Reviewer:                   |      Merged:                                   
         
Work_issues:                   |  
-------------------------------+--------------------------------------------

Comment(by drkirkby):

 Replying to [comment:58 malb]:
 > > The only issue with removing these 2 targets may be the optional
 Macaulay2 spkg. We > have some discussions atm in gentoo about singular -
 the components it provides -
 > > and Macaulay2. So while sage builds ok, Macaulay2 should be checked.
 >
 > I'm pretty sure Macaulay2 will fail if we drop libfac and libcf. Thus
 I'm not applying the second patch for now.

 It would be good if this Macaulay2 could be made to rebuild Singular in
 this case. Perhaps have an environment variable that determines if those
 two targets are built or not.
 {{{
 build()
 {
     patch
     distclean
     config
     build_singular
     build_libsingular
     if [ "x$SAGE_USING_Macaulay2" = xyes  ] ; then
        build_factory
        build_libfac
     fi
     create_singular_script
     install_docs
 }
 }}}
 Then ensure Macaulay2

  * exports SAGE_USING_Macaulay2 = "yes"
  * Rebuilds Singular. This time build_factory & build_libfac would built,
 due to the environment variable being set to "yes"

 I guess this depends on the popularity of Macaulay2. If 20% of people
 install it, then we might as well build all targets. If however only 1% of
 people install Macaulay2, then I doubt it warrants slowing the build
 process for everyone.

 Currently I believe Singular is the slowest package to build in Sage (at
 least on my !OpenSolaris machine), though neither R or Maxima are
 building, so I can't say for sure. But Singular definately takes a long
 time to build, so if that could be improved, it would be nice. Of course,
 it depends on how long those targets take to build. If the savings from
 not building them are only small, we might as well build them.

 Another option might be to let an environment variable be used to stop
 those two targets building, but by default build them all.

 Dave

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