#8059: Update Singular spkg to release 3-1-1-4
-------------------------------------------------------+--------------------
 Reporter:  malb                                       |         Owner:         
                                               
     Type:  enhancement                                |        Status:  closed 
                                               
 Priority:  major                                      |     Milestone:  
sage-4.5.3                                            
Component:  packages                                   |    Resolution:  fixed  
                                               
 Keywords:                                             |        Author:  Martin 
Albrecht                                       
 Upstream:  Reported upstream. Little or no feedback.  |      Reviewer:  David 
Kirkby, Simon King, William Stein, John Palmieri
   Merged:  sage-4.5.3.alpha1                          |   Work_issues:         
                                               
-------------------------------------------------------+--------------------

Comment(by drkirkby):

 Replying to [comment:127 leif]:
 > ''Almost all'' generated files ({{{configure}}}, {{{grammar.cc}}} etc.)
 '''again''' carry the same time stamp as their sources... :(

 I don't know what method they use to create the tarball, but its hard to
 see how this can happen. Unless they touch all files before releasing,
 it's hard to understand how they can created a configure script with the
 same timestamp as the file it is generated from.

 Perhaps they copy them with {{{cp}}} at one point, and don't preserve
 modification times ({{{cp -p}}}). Whatever it is they are doing, it is
 wrong.


 > I wonder if we should touch ''all of them'' in {{{spkg-install}}}, not
 just two.

 Anything that should be touched should be.

 > <flame>
 > I thought the upstream developers had learned at Sage Days 23.5, but
 perhaps 3.1.1.4 was just prepared too early...
 > </flame>

 No comment.


 BTW, is this really 3-1-1-4, or is it a snapshot? If the latter, then it's
 quite possible someone in the Sage community created the configure script
 and did not preserve modification times. In which case, the upstream
 developers are not to blame.


 Dave

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