On Sun, Sep 23, 2012 at 9:40 AM, Volker Braun wrote:
> LibGAP (the C library interface to GAP) is finally usable and ready to be
> released into the wild! We will ship it as a separate spkg since
> * Upstream doesn't build a shared library
> * The build system is replaced by standard autotools
>LibGAP (the C library interface to GAP) is finally usable and
>ready to be released into the wild!
Yippee!!! That will make such a difference!
>Per the usual rules, new spkgs need a vote so now is your chance to be
>heard ;-)
+1 without a question.
Thanks!
On Sep 23, 2012, at 06:40 , Volker Braun wrote:
> LibGAP (the C library interface to GAP) is finally usable and ready to be
> released into the wild! We will ship it as a separate spkg since
> * Upstream doesn't build a shared library
> * The build system is replaced by standard autotools
> *
On Sun, Sep 23, 2012 at 6:40 AM, Volker Braun wrote:
> LibGAP (the C library interface to GAP) is finally usable and ready to be
> released into the wild! We will ship it as a separate spkg since
> * Upstream doesn't build a shared library
> * The build system is replaced by standard autotools
Le 23/09/2012 15:40, Volker Braun a écrit :
Per the usual rules, new spkgs need a vote so now is your chance to be
heard ;-)
+1 direct interface is so much better than through a pexpect...
Snark on #sagemath
--
You received this message because you are subscribed to the Google Groups
"sage-
On 23 September 2012 14:40, Volker Braun wrote:
> LibGAP (the C library interface to GAP) is finally usable and ready to be
> released into the wild! We will ship it as a separate spkg since
> * Upstream doesn't build a shared library
> * The build system is replaced by standard autotools
>
On Sun, Sep 23, 2012 at 9:40 AM, Volker Braun wrote:
> LibGAP (the C library interface to GAP) is finally usable and ready to be
> released into the wild! We will ship it as a separate spkg since
...
>
> Per the usual rules, new spkgs need a vote so now is your chance to be heard
> ;-)
>
+1
>
