Re: [sage-devel] Re: Sage 5.11.beta3 and debian package: ptestlong results

Le 06/07/2013 14:27, Volker Braun a écrit : On Saturday, July 6, 2013 1:02:54 AM UTC-4, Snark wrote: Do we really need nef.x, poly.x, etc. ; I mean if the executables names don't reflect what they are good for, perhaps we (both in sage and in debian) should stick to -d.x variants?

Re: [sage-devel] Re: Sage 5.11.beta3 and debian package: ptestlong results

On Saturday, July 6, 2013 1:02:54 AM UTC-4, Snark wrote: > Do we really need nef.x, poly.x, etc. ; I mean if the executables names > don't reflect what they are good for, perhaps we (both in sage and in > debian) should stick to -d.x variants? In principle we don't need an unnumbered poly.x,

Re: [sage-devel] Re: Sage 5.11.beta3 and debian package: ptestlong results

Le 06/07/2013 03:30, Volker Braun a écrit : On Friday, July 5, 2013 3:42:13 PM UTC-4, Snark wrote: - 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), whe

Re: [sage-devel] Re: Sage 5.11.beta3 and debian package: ptestlong results

On Friday, July 5, 2013 3:42:13 PM UTC-4, Snark wrote: > - 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 ; > Sounds good, I take it that it installs

Re: [sage-devel] Re: Sage 5.11.beta3 and debian package: ptestlong results

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. U

Re: [sage-devel] Re: Sage 5.11.beta3 and debian package: ptestlong results

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

Re: [sage-devel] Re: Sage 5.11.beta3 and debian package: ptestlong results

Le 05/07/2013 20:09, Volker Braun a écrit : On Thursday, July 4, 2013 2:26:02 PM UTC-4, Snark wrote: (1) My debian package only ships the dimension 11-enabled executables ; Just to confirm, that is useless. Palp needs to be complied for different dimensions. Ok. And you need to be care

Re: [sage-devel] Re: Sage 5.11.beta3 and debian package: ptestlong results

On Thursday, July 4, 2013 2:26:02 PM UTC-4, Snark wrote: > (1) My debian package only ships the dimension 11-enabled executables ; > Just to confirm, that is useless. Palp needs to be complied for different dimensions. And you need to be careful with filesystem timestamp granularity if you wan

Re: [sage-devel] Re: Sage 5.11.beta3 and debian package: ptestlong results

Le 04/07/2013 19:07, Andrey Novoseltsev a écrit : On Thursday, 4 July 2013 10:44:40 UTC-6, Snark wrote: Le 04/07/2013 17:04, Andrey Novoseltsev a ďż˝crit : > Regarding PALP breaking or not - it has different speed and capabilities > depending on compile-time limits. Sage packag

Re: [sage-devel] Re: Sage 5.11.beta3 and debian package: ptestlong results

On Thursday, 4 July 2013 10:44:40 UTC-6, Snark wrote: > > Le 04/07/2013 17:04, Andrey Novoseltsev a �crit : > > Regarding PALP breaking or not - it has different speed and capabilities > > depending on compile-time limits. Sage package actually compiles several > > versions of it and adds maxi

Re: [sage-devel] Re: Sage 5.11.beta3 and debian package: ptestlong results

Le 04/07/2013 17:04, Andrey Novoseltsev a écrit : Regarding PALP breaking or not - it has different speed and capabilities depending on compile-time limits. Sage package actually compiles several versions of it and adds maximum dimension to executable file names. It is probably quite incompatible

[sage-devel] Re: Sage 5.11.beta3 and debian package: ptestlong results

Regarding PALP breaking or not - it has different speed and capabilities depending on compile-time limits. Sage package actually compiles several versions of it and adds maximum dimension to executable file names. It is probably quite incompatible with what any distribution does. Andrey -- Yo