On 2013-10-26, at 16:50, juanjose.garciarip...@gmail.com wrote:
I am also able to build with Xcode 5.0.1 (5A2053) - again with the command
line tools installed. Note: I also have the homebrew versions of automake,
autoconf and libtool installed.
This is because I uploaded some fixes
On 2013-10-17, at 19:58, Jon Boone ipmon...@gmail.com wrote:
Juanjo,
When you say that the existing tree does not work with upcoming Xcode, which
version do you mean? I have Xcode 5.0 (5A1413) and was able to build ECL
just fine once I installed the command line tools.
I am also able
I am also able to build with Xcode 5.0.1 (5A2053) - again with the command line
tools installed. Note: I also have the homebrew versions of automake,
autoconf and libtool installed.
This is because I uploaded some fixes that corrected whatever problems there
were, but there was a bug
Dear all,
my only use of ECL so far is to run Maxima, as a part of Sage, or standalone,
so let me stick to the issues that affect this use. In particular ECL
is very valuable for Sage and
is much appreciated among Sage developers, as far as I know.
On 7 October 2013 09:54, Juan Jose Garcia-Ripoll
On Fri, 18 Oct 2013 21:04:10 +0100
Dima Pasechnik dimpase+...@gmail.com wrote:
I don't know what makes one think that LGPLv3 has issues with web
applications.
This applies to AGPL, but not to LGPL, as far as I know.
You are right about the AGPL, however, the LGPL3 license inherits from
the
Juanjo,
When you say that the existing tree does not work with upcoming Xcode, which
version do you mean? I have Xcode 5.0 (5A1413) and was able to build ECL just
fine once I installed the command line tools.
--jon
15.10.2013, 11:54, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
On Sat, Oct 12, 2013 at 12:56 AM, Anton Vodonosov avodono...@yandex.ru
wrote:
Juan Jose, how about publishing the changes already in git as the last
release?
So that future users use and discuss a version as close
07.10.2013, 12:55, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
* On a similar line, if integrating third-party libraries becomes an issue,
they will be completely dropped or frozen. For instance, ECL may end up
demanding
that you install libffi or libgc, leaving an old but
Dear Juanjo,
Thank you very much for your diligent and hard work over such a long period
of time!
It is very sad to hear about your decision. But as you say: sometimes it
is better to accept reality than to fight against it.
* First of all, ECL no longer relates to my own work. On the
Hi
On 10 October 2013 23:51, Matthew Mondor mm_li...@pulsar-zone.net wrote:
On Mon, 7 Oct 2013 10:54:01 +0200
Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com wrote:
[...]
* I am not going to change ECL's license. LGPL3's restrictions on web
applications seem stupid to me and, as
Juan Jose, how about publishing the changes already in git as the last release?So that future users use and discuss a version as close to git repository as possible. 07.10.2013, 12:55, "Juan Jose Garcia-Ripoll" juanjose.garciarip...@gmail.com:Hi everybody, as you may have noticed, my level of
On Mon, 7 Oct 2013 10:54:01 +0200
Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com wrote:
* The consequence is that the time I can devote to ECL has serious ups and
downs. In an environment of rapidly developing tools and libraries, this is
quite unfortunate, as the project may lag
On Thu, 10 Oct 2013 17:51:14 -0400
Matthew Mondor mm_li...@pulsar-zone.net wrote:
On Mon, 7 Oct 2013 10:54:01 +0200
Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com wrote:
* I am not going to change ECL's license. LGPL3's restrictions on web
applications seem stupid to me and, as
Hi everybody,
as you may have noticed, my level of responsiveness in the last months has
gone down to almost zero. At the beginning I expected it would be
transitory, but it seems that it is here to stay. The situation is such
that I decided to write this email, both as an explanation and also to
14 matches
Mail list logo
