#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 leif):
Replying to [comment:129 AlexanderDreyer]:
> > ''Almost all'' generated files ({{{configure}}}, {{{grammar.cc}}}
etc.) '''again''' carry the same time stamp as their sources... :(
>
> These files '''can''' be generated, but there is no need to do so (if
you are not a Singular-kernel developer). In fact they are pre-generated
in the repo:
> http://www.singular.uni-kl.de/svn/trunk/
> (That's why the time stamps are equal.)
And exactly '''that''' can (and did) cause problems; the distributed
generated files should be
* '''newer''' than their sources,
* up-to-date.
See http://trac.sagemath.org/sage_trac/ticket/9160#comment:22 (and
http://trac.sagemath.org/sage_trac/ticket/9160#comment:20 for the latter
issue, or the whole ticket...) and also [http://groups.google.com/group
/sage-devel/browse_thread/thread/fbf5b7f781c3f523# this thread on sage-
devel].
Unfortunately we hadn't had the time to add more comments on this to
{{{SPKG.txt}}}, but I expected the people further working on the Singular
spkg to be aware of these issues, or take a look at previous tickets
related to the spkg. (And I didn't edit the SD 23.5 wiki page, because at
that time it didn't seem appropriate, but asked for other people
propagating these things.)
> The reason for this is that the generators for these files (e.g.
'''specific''' version of autotools and lex) are not available on all
supported platforms.
>
> Of course, there are attempts to change this, but this cannot be done
within 2,5 days. If (and only if) the tools of Sage distribution are
capable of generating these files, then the correct solution would be to
to remove them complete during patching.
>
> > <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>
> This wasn't at topic at SD23.5.
Obviously unfortunately not, see above. I expected it to be one.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8059#comment:131>
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.
