Artistic Licensing of Alan v2

57 views
Skip to first unread message

Rémi Verschelde

unread,
Jul 25, 2013, 3:52:17 AM7/25/13
to tho...@alanif.se, gargl...@googlegroups.com, bcre...@gmail.com, sto...@mageia.org, be...@beuc.net
Hi Thomas,

I'm one of the packagers of Gargoyle for Mageia, which includes per
policy only free software in its gargoyle-free package.
I've been in touch with Ben Cressey (Gargoyle developer) and Sylvain
Beucler (Debian packager of Gargoyle) to discuss the licensing of Alan
v2, and its possible inclusion in the free software version of
Gargoyle.

Sylvain told me he was already in contact with you in February 2012,
and that you confirmed that the Artistic License 2.0 applies not only
for Alan v3 but also for the obsoleted v2.

As the licensing policies for Debian and Mageia are quite rigid, we
would need a public statement of this and an access to the latest
version of the source code to be able to include Alan v2 in
gargoyle-free. As of today (July 25th, 2013), the archive for the Alan
v2 interpreter source code is broken, see:
http://www.alanif.se/files/v2download/interpreter287src.tgz

Could I ask you to update the Alan v2 web pages, manual and/or (at
best) source code to confirm this change of licensing, and to upload a
working tarball of the interpreter's source on your website?

Many thanks,
Rémi Verschelde (Akien)

Sylvain

unread,
Sep 15, 2013, 4:07:28 AM9/15/13
to gargl...@googlegroups.com
[Forwarding Thomas' reply to the list - it didn't make it AFAICS.]

- Sylvain

On Sat, Jul 27, 2013 at 06:23:56PM +0200, Thomas Nilsson wrote:
> Hi R�mi!
>
> Yes it is true that the licensing for Alan V2 is also AL2.0 bit as you say, this has ponly been comunicated through private email conversations as of now. I will make sure there is a not of this in the Alan v2 download area of the web site too.
>
> As for the non-working source download, sorry for that. I tried to rush a zip file together before going on a weeks trip away from home, but failed. The makefiles doesn't even work with my current setup (and possibly newer GnU tools). I'll try to fix a zip when
> I get back next week. I suppose you are only in need of the interpreter source, right?
>
> Thomas Nilsson
> Alan designer and developer
> > R�mi Verschelde (Akien)

Samuel Verschelde

unread,
Sep 15, 2013, 4:09:38 AM9/15/13
to gargl...@googlegroups.com
Just in case it's useful I can confirm that this e-mail is genuine. I was in CC
when Thomas Nilsson sent it to Rémi, Sylvain and Ben.

Samuel

Le dimanche 15 septembre 2013 10:07:28, Sylvain a écrit :
> [Forwarding Thomas' reply to the list - it didn't make it AFAICS.]
>
> - Sylvain
>
> On Sat, Jul 27, 2013 at 06:23:56PM +0200, Thomas Nilsson wrote:
> > Hi Rémi!
> > > Rémi Verschelde (Akien)

Rémi Verschelde

unread,
Jan 19, 2014, 5:56:27 PM1/19/14
to gargl...@googlegroups.com, Verschelde Samuel, be...@beuc.net
CC'ing the garglk-dev ML, Sylvain and Samuel. Great news!


2014/1/19 Thomas Nilsson <tho...@alanif.se>
>
> Hi Rémi!
>
> I have finally taken the time to go through old repositories and managed to put together a working source package for the Alan 2.8(7) interpreter. I have also updated the v2download page to clearly state that the v3 licensing also applies to v2. Unfortunately I won't have the time or energy to update all the old sources to state the same.
>
> I hope that will clarify the matter and enable alan2 to join the Gargoyle-free family!
>
> I don't know if you, or maybe Ben, can help me with a small issue. As Alan v3 progresses some bugs are identified and fixed, and since Gargoyle have a slow maintenance cycle ;-) I have been trying to provide slot-in replacements for the alan3 'terp. On windows and MacOS I have been completely successful. But for Linux (Ubuntu 13.10 specifically) I have yet to succeed. Seems the Linux 'terps are not build against libgarglk.so, or are working some magic that escapes me, because when I build the 2011.1 Gargoyle sources the binaries that I get don't work when they are replacing the ones in the Gargoyle distribution. 'ldd' indicates that the alan3 binary distributed has dependencies directly to all the libs, but not to libgarglk.so. What am I missing?
>
> Regards,
> Thomas
>
> AlanIF designer and maintainer
> http://www.alanif.se
>
> Rémi Verschelde
> den 25 juli 2013 09:52

Sylvain

unread,
Jan 20, 2014, 2:22:19 PM1/20/14
to Rémi Verschelde, gargl...@googlegroups.com, Verschelde Samuel
Hi Thomas and thanks for the update!
About your question:

> 2014/1/19 Thomas Nilsson <tho...@alanif.se>
> > I don't know if you, or maybe Ben, can help me with a small
> > issue. As Alan v3 progresses some bugs are identified and fixed,
> > and since Gargoyle have a slow maintenance cycle ;-) I have been
> > trying to provide slot-in replacements for the alan3 'terp. On
> > windows and MacOS I have been completely successful. But for Linux
> > (Ubuntu 13.10 specifically) I have yet to succeed. Seems the Linux
> > 'terps are not build against libgarglk.so, or are working some
> > magic that escapes me, because when I build the 2011.1 Gargoyle
> > sources the binaries that I get don't work when they are replacing
> > the ones in the Gargoyle distribution. 'ldd' indicates that the
> > alan3 binary distributed has dependencies directly to all the
> > libs, but not to libgarglk.so. What am I missing?

For simplicity, and because no other package uses libglk, libgarglk.so
is statically compiled; so it's not installed anywhere, it's just
bundled into each terp executable.

Here's what I've written in the Debian/Ubuntu build file:

# Tell 'jam' to statically link private libraries; the convenience
# library is pretty small and it's much simpler in jam than trying to
# install to a private library prefix directory (would be
# /usr/lib/gargoyle) - or using a LD_LIBRARY_PATH wrapper.
export STATIC=1

Instead you could provide an updated (static) /usr/lib/gargoyle/alan3
:)

Cheers!
Sylvain

Rémi Verschelde

unread,
Jan 20, 2014, 2:31:20 PM1/20/14
to Sylvain, Thomas Nilsson, Ben Cressey, gargl...@googlegroups.com, Verschelde Samuel
Forwarding Sylvain's answer to Thomas.

2014/1/20 Sylvain <be...@beuc.net>:
Reply all
Reply to author
Forward
0 new messages