Le 05/07/2013 21:24, Volker Braun a écrit :
On Friday, July 5, 2013 3:06:55 PM UTC-4, Snark wrote:
> And you need to be careful with filesystem
> timestamp granularity if you want to do that programmatically,
see the
> palp spkg.
I don't understand what you mean at all.
Unless you exactly follow what the spkg does I'd recommend you try on a
build host with an older filesystem...
If that remark is about the fact that the spkg patches the value of
POLY_Dmax using sed and that can be a problem, see below.
> autotools doesn't really support that either). For better or
worse, Sage
> will have to build its own palp for the forseeable future.
I beg to disagree: the next upload of a palp package in debian will be
sage-compatible.
Because you essentially forked palp. I'm happy with pushing sage-palp
into debian, but if you use upstream code then it won't work.
In fact, my package:
- has a patch, forwarded upstream, which makes it easy to compile PALP
with various POLY_Dmax values, since it's a matter of adding
-DPOLY_Dmax=<num> to the compile lines ;
- provides its own set of configure.ac + GNUmakefile.am, which were
forwarded upstream last time (but I still have to do it again with the
latest changes), where I added the various targets ;
- provides its own manpages, which were forwarded upstream (but I still
have to do it again with the latest changes).
I need to find the time to write an email to upstream about the latest
news, and to the debian-science mailing-list to ask for a sponsor for
the new package... things are pending.
Why does sage use 6 as a default when upstream uses 7 ?
Snark on #sagemath
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
