Re: [sage-devel] add curl as a standard package

On Monday, October 24, 2016 at 9:45:18 PM UTC, Emmanuel Charpentier wrote: > > Okay. I I have followed you correctly, we have two (mutually incompatible) > options : > > >- (Dima's option) : package curl, pcre and xz as standard packages, >and make R depend on them (unconditionnally). >

Re: [sage-devel] add curl as a standard package

Okay. I I have followed you correctly, we have two (mutually incompatible) options : - (Dima's option) : package curl, pcre and xz as standard packages, and make R depend on them (unconditionnally). - (Jean-Pierre option) : add tjem to Sage's core, but build them if and only if the

Re: [sage-devel] Error installing package iml-1.0.4p1.p1

On 2016-10-24 18:41, tieno...@gmail.com wrote: Thank you for the advise. Just one question. How can I debug with the sage subshell? How is it possible to use it? The idea is to manually run things like configure or make (inside the package build directory, which is in local/var/tmp/sage/build)

Re: [sage-devel] add curl as a standard package

On 2016-10-24 18:39, Emmanuel Charpentier wrote: Bonus question for the build system experts : can an spkg-install script recursively call $SAGE_ROOT/sage -i and get the return status back ? A simple solution would then be to test for the existence of the relevant binaries/executables in the R s

[sage-devel] Re: add pcre as a standard package

On Monday, October 24, 2016 at 4:35:32 PM UTC, Emmanuel Charpentier wrote: > > Le lundi 24 octobre 2016 16:14:29 UTC+2, Dima Pasechnik a écrit : >> >> +1 >> >> IMHO we don't really have to vote on it, as this is basically splitting >> of a standard package into several, >> as enforced by upstrea

Re: [sage-devel] add curl as a standard package

On Monday, October 24, 2016 at 8:47:13 PM UTC+2, Jean-Pierre Flori wrote: > > > > On Monday, October 24, 2016 at 6:39:27 PM UTC+2, Emmanuel Charpentier > wrote: >> >> Bonus question for the build system experts : can an spkg-install script >> recursively call $SAGE_ROOT/sage -i and get the ret

Re: [sage-devel] add curl as a standard package

On Monday, October 24, 2016 at 6:39:27 PM UTC+2, Emmanuel Charpentier wrote: > > Bonus question for the build system experts : can an spkg-install script > recursively call $SAGE_ROOT/sage -i and get the return > status back ? A simple solution would then be to test for the existence of > the

Re: [sage-devel] add curl as a standard package

On Monday, October 24, 2016 at 4:39:27 PM UTC, Emmanuel Charpentier wrote: > > Bonus question for the build system experts : can an spkg-install script > recursively call $SAGE_ROOT/sage -i and get the return > status back ? A simple solution would then be to test for the existence of > the r

Re: [sage-devel] Error installing package iml-1.0.4p1.p1

Thank you for the advise. Just one question. How can I debug with the sage subshell? How is it possible to use it? On Monday, October 24, 2016 at 2:49:03 PM UTC+2, Jeroen Demeyer wrote: > > On 2016-10-24 14:33, tien...@gmail.com wrote: > > I tried to build Sage with Debian packages. I followed

Re: [sage-devel] add curl as a standard package

Bonus question for the build system experts : can an spkg-install script recursively call $SAGE_ROOT/sage -i and get the return status back ? A simple solution would then be to test for the existence of the relevant binaries/executables in the R spkg-install script, and recursively install the

[sage-devel] Re: add pcre as a standard package

Le lundi 24 octobre 2016 16:14:29 UTC+2, Dima Pasechnik a écrit : > > +1 > > IMHO we don't really have to vote on it, as this is basically splitting of > a standard package into several, > as enforced by upstream. > Indeed. However, the suggestion made on the similar stream on curl (i. e. instal

[sage-devel] Mercurial in "Sage developers's guide (Release 7.4)"

There remain some references to Mercurial in the developer's guide: -page 114: "Overview of Patching SPKGS:" ..., use Mercurial to checck... -page 115, -near top: The Mercurial configuration file ... -in the last paragraph: ... use Mercurial... hg tag... t.d. -- You

[sage-devel] Re: Coxeter3 problem.

I also get this as well. I believe I have become the official spkg maintainer, and I will fix it within a day. Best, Travis On Monday, October 24, 2016 at 2:46:28 AM UTC-5, tdumont wrote: > > > Coxeter3 cannot be compiled (7.4 and 7.5beta0). > > Actually this does not seem too difficult (a func

[sage-devel] Re: add pcre as a standard package

+1 IMHO we don't really have to vote on it, as this is basically splitting of a standard package into several, as enforced by upstream. On Monday, October 24, 2016 at 10:12:01 AM UTC, Emmanuel Charpentier wrote: > > [ Same problem as for curl, posted a few seconds ago ] > > It looks like pcre <

Re: [sage-devel] Re: Notebook stuck on "N?" with a worksheet

I have a setup helper for jupyterhup at https://github.com/vbraun/run-jupyter-hub It might be out of date, haven't tried it with the newest version of jupyterhub. But maybe its a starting point for you... On Monday, October 24, 2016 at 7:47:15 AM UTC-4, Jori Mäntysalo wrote: > > On Sun, 23 O

Re: [sage-devel] add curl as a standard package

On 10/24/2016 09:46 AM, Emmanuel Charpentier wrote: > > Not the same problem. To detect curl, it is enough to find an executable > named "curl" in the path. As far as I know, R uses a library, and this > is known to be not so easy to find. > Which library does R link against? If you can find out

Re: [sage-devel] add curl as a standard package

Maybe it is not that bad if the automagic detection system is not that good. If the automatic stuff works magically on usual config, let's say large Linux distros, that's enough. As long as we have "--with-x" options to pass to configure for making Sage more distro friendly and let smart people d

Re: [sage-devel] add curl as a standard package

Le lundi 24 octobre 2016 15:31:36 UTC+2, Michael Orlitzky a écrit : > > On 10/24/2016 06:41 AM, Vincent Delecroix wrote: > > In between? > > > > * having a curl pacakge that will be installed if not present on the > > system (~the same way we deal with gcc) > > > > And the same for pcre an

Re: [sage-devel] add curl as a standard package

Le lundi 24 octobre 2016 12:41:14 UTC+2, vdelecroix a écrit : > > In between? > > * having a curl pacakge that will be installed if not present on the > system (~the same way we deal with gcc) > Great idea, if I can implement it. Looking in the $PATH is not quite easy to do portably. I'm cu

Re: [sage-devel] add curl as a standard package

On 10/24/2016 06:41 AM, Vincent Delecroix wrote: > In between? > > * having a curl pacakge that will be installed if not present on the > system (~the same way we deal with gcc) > And the same for pcre and xz. Check for it in ./configure, and give us a way to override it, like --with-xz[=path].

Re: [sage-devel] Re: Notebook stuck on "N?" with a worksheet

On Monday, October 24, 2016 at 11:47:15 AM UTC, Jori Mäntysalo wrote: > > On Sun, 23 Oct 2016, Luca De Feo wrote: > > >> As far as I know, Jupyter(hub) does not have such a feature since it > >> completely relies on the OS for access checks. > > > > That's not correct. JupyterHub supports arb

Re: [sage-devel] Error installing package iml-1.0.4p1.p1

On 2016-10-24 14:33, tieno...@gmail.com wrote: I tried to build Sage with Debian packages. I followed the method on the wiki . I suggest that you write to the Debian mailing list: https://lists.alioth.debian.org/mailman/

[sage-devel] Error installing package iml-1.0.4p1.p1

I tried to build Sage with Debian packages. I followed the method on the wiki . When I run "debian/rules prune build", I got the following error: Host system: Linux etienne 4.5.0-0.bpo.1-amd64 #1 SMP Debian 4.5.1-1~bpo8

[sage-devel] Error installing package iml-1.0.4p1.p1

Host system: Linux etienne 4.5.0-0.bpo.1-amd64 #1 SMP Debian 4.5.1-1~bpo8+1 (2016-04-20) x86_64 GNU/Linux gcc version 4.9.2 (Debian 4.9.2-10) checking for GMP >= 3.1.1... not found configure: error: GMP not found! GMP version 3.1.1 or greater is required for this library to compile. Please make

Re: [sage-devel] Re: Notebook stuck on "N?" with a worksheet

On Sun, 23 Oct 2016, Luca De Feo wrote: As far as I know, Jupyter(hub) does not have such a feature since it completely relies on the OS for access checks. That's not correct. JupyterHub supports arbitrary authenticators: https://jupyterhub.readthedocs.io/en/latest/authenticators.html Can

Re: [sage-devel] add curl as a standard package

In between? * having a curl pacakge that will be installed if not present on the system (~the same way we deal with gcc) Vincent -- 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, s

[sage-devel] Re: add pcre as a standard package

s/curl/pcre/g... Damn... -- Emmanuel Charpentier Le lundi 24 octobre 2016 12:12:01 UTC+2, Emmanuel Charpentier a écrit : > > [ Same problem as for curl, posted a few seconds ago ] > > It looks like pcre , which > was formerly installed by R installa

[sage-devel] add pcre as a standard package

[ Same problem as for curl, posted a few seconds ago ] It looks like pcre , which was formerly installed by R installation, must now be installed in order to ins

[sage-devel] add curl as a standard package

It looks like curl , which was formerly installed by R installation, must now be installed in order to install R. One can note that a problem will rarely exists, since most Sage users

[sage-devel] Re: Error installing package ecl-16.1.2.p1

On Sunday, October 23, 2016 at 11:03:52 PM UTC, tien...@gmail.com wrote: > > *Host system:* > Linux etienne 4.5.0-0.bpo.1-amd64 #1 SMP Debian 4.5.1-1~bpo8+1 > (2016-04-20) x86_64 GNU/Linux > > *C compiler:* gcc > *C compiler version*: gcc (Debian 4.9.2-10) 4.9.2 [It is built-in specs] > > *Error

[sage-devel] Re: Make xz a standard package ?

+1 On Sunday, October 23, 2016 at 3:15:19 PM UTC, Emmanuel Charpentier wrote: > > The xz package has been part of Sage for about three months (see > Trac#21063 ). Making it stanrd > would simplify handling of tarballs (see Trac#18236 >

[sage-devel] Coxeter3 problem.

Coxeter3 cannot be compiled (7.4 and 7.5beta0). Actually this does not seem too difficult (a function has been has been declared twice with the same signature). May be it's better that the spkg maintainer (Mike Hansen) correct this than me. t.d. -- You received this message because you are