#17254: Upgrade to Singular-4-0-1
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.4
Component: packages: | Resolution:
standard | Merged in:
Keywords: | Reviewers:
Authors: | Work issues:
Report Upstream: N/A | Commit:
Branch: | 3a512cd7e08e21a4a4e66bfe9179290601717ba0
u/jakobkroeker/ticket.17254.squashed| Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by fbissey):
It is expected for that directory not to exist for you. Whoever wrote the
patch was working in a folder named `latest` but it is their own naming.
It doesn't matter anyway. Let me explain to you how the `-p` option of
patch works.
Your patch has a header that helps you locate the file to patch:
{{{
--- latest/Singular/run.c 2014-11-19 14:06:05.000000000 +0100
+++ latest/Singular/run.c 2015-01-16 09:32:45.771298300 +0100
}}}
`patch < mypatch.patch` or equivalently `patch -p0< mypatch.patch` will
look for the file
`latest/Singular/run.c` relative to where patch is executed. `-pN` will
strip the `N` first folders in front of the file name so
`patch -p1< mypatch.patch` will look for `Singular/run.c`. In `spkg-
install` for singular, patches are applied with `patch -p1 <"$patch"` so
you shouldn't care about `latest` it is discarded. Look for
`local/var/tmp/sage/build/singular-4.0.1p1.p0/src/Singular/run.c` OK?
--
Ticket URL: <http://trac.sagemath.org/ticket/17254#comment:39>
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.
For more options, visit https://groups.google.com/d/optout.
