Re: Portability of Drakma

On 3/9/07, Edi Weitz <edi <at> agharta.de> wrote:
> On Mon, 5 Mar 2007 08:54:57 +0100, "Erik Huelsmann" <ehuels <at> gmail.com> wrote:
>
> > I created a patch (and a full archive) for drakma 0.6.0. I did
> > initial testing with usocket 0.3.2 and sbcl on linux 2.6. I'll put
> > up a text file at the same location to log the already-tested
> > combinations. The archive is at http://hix.nu/drakma/ (which is
> > behind my dsl line at 1Mbit).
> >
> > Version 0.3.2 for usocket is required: I added the
> > close-the-stream-means-closing-the-socket API guarantee in that
> > version.
> >
> > Any problems with usocket can be reported directly to me, here (for
> > reference for other testers), or at usocket-devel <at> common-lisp.net.
> >
> > I'll be testing a number of other combinations too, but I was out of
> > time this weekend.
>
> Did you get any more test results in the meantime?

I did. I tested with LispWorks, Allegro 8, cmucl, ecl and clisp on Linux.

My clisp was incompatible with cl+ssl, so I'll post more results
later. ECL isn't compatible with trivial-gray-streams, it seems.

The other 3 worked without problems.

Leaves OpenMCL (which I can't test) and LispWorks and Allegro on
Windows (which I'll post about later, since I'm in Linux now).

Re: Portability of Drakma

On 4/6/07, Erik Huelsmann <ehuels <at> gmail.com> wrote:
> On 3/9/07, Edi Weitz <edi <at> agharta.de> wrote:
> > On Mon, 5 Mar 2007 08:54:57 +0100, "Erik Huelsmann" <ehuels <at> gmail.com> wrote:
> >
> > > I created a patch (and a full archive) for drakma 0.6.0. I did
> > > initial testing with usocket 0.3.2 and sbcl on linux 2.6. I'll put
> > > up a text file at the same location to log the already-tested
> > > combinations. The archive is at http://hix.nu/drakma/ (which is
> > > behind my dsl line at 1Mbit).
> > >
> > > Version 0.3.2 for usocket is required: I added the
> > > close-the-stream-means-closing-the-socket API guarantee in that
> > > version.
> > >
> > > Any problems with usocket can be reported directly to me, here (for
> > > reference for other testers), or at usocket-devel <at> common-lisp.net.
> > >
> > > I'll be testing a number of other combinations too, but I was out of
> > > time this weekend.
> >
> > Did you get any more test results in the meantime?
>
> I did. I tested with LispWorks, Allegro 8, cmucl, ecl and clisp on Linux.
>
> My clisp was incompatible with cl+ssl, so I'll post more results
> later. ECL isn't compatible with trivial-gray-streams, it seems.
>
> The other 3 worked without problems.
>
> Leaves OpenMCL (which I can't test) and LispWorks and Allegro on

Re: Portability of Drakma

On Fri, 6 Apr 2007 14:43:30 +0200, "Erik Huelsmann" <ehuels <at> gmail.com> wrote:

> Ok. I tested on Windows too. I have LispWorks and ACL 6.2 on
> Windows.  The latter doesn't work with start.lisp from STARTER-PACK

Sure.  STARTER-PACK is only for LispWorks.

For AllegroCL, you'd have to figure out a way to locate the ASDF
systems.  FWIW, the relevant parts of my ~/.clinit.cl on Windows look
like this:

  (in-package :cl-user)

  (require :asdf)

  #+:asdf
  (dolist (dir-candidate (directory "c:/home/lisp/*" :directories-are-files nil))
    (when (excl:file-directory-p dir-candidate)
      (let ((asd-candidate (merge-pathnames "*.asd" dir-candidate)))
        (when (directory asd-candidate)
          (push dir-candidate asdf:*central-registry*)))))

That should slurp in all "c:/home/lisp/*/*.asd" system definitions.

> That was all the testing I can do. BTW: the CL+SSL problems I
> experienced were with the newest clisp (2.41), so it looks like
> Drakma isn't able to run on clisp anymore (?).

Hmm, maybe the CLISP users on this list should try and report to the
CL+SSL mailing list if necessary.  I personally don't use CLISP.

Re: Re: Portability of Drakma

Scribit Edi Weitz dies 06/04/2007 hora 15:30:
> I guess that some people would eventually be interested in SBCL/Win,
> but I don't know how mature it is.

Threads are not working yet, so it's not a valid choice for using
Hunchentoot, I suppose. It may be possible to test it's compatibility,
though.

Quickly,
Pierre
--

-- 
nowhere.man <at> levallois.eu.org
OpenPGP 0xD9D50D8A

_______________________________________________
drakma-devel mailing list
drakma-devel <at> common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/drakma-devel

Re: Re: Portability of Drakma

On Fri, 6 Apr 2007 16:19:26 +0200, Pierre THIERRY <nowhere.man <at> levallois.eu.org> wrote:

> Threads are not working yet, so it's not a valid choice for using
> Hunchentoot, I suppose.

Sure, but this is the Drakma mailing list... :)

Re: Portability of Drakma

On 4/6/07, Edi Weitz <edi <at> agharta.de> wrote:
> On Fri, 6 Apr 2007 14:43:30 +0200, "Erik Huelsmann" <ehuels <at> gmail.com> wrote:
>
> > Ok. I tested on Windows too. I have LispWorks and ACL 6.2 on
> > Windows.  The latter doesn't work with start.lisp from STARTER-PACK
>
> Sure.  STARTER-PACK is only for LispWorks.
>
> For AllegroCL, you'd have to figure out a way to locate the ASDF
> systems.  FWIW, the relevant parts of my ~/.clinit.cl on Windows look
> like this:
>
>   (in-package :cl-user)
>
>   (require :asdf)
>
>   #+:asdf
>   (dolist (dir-candidate (directory "c:/home/lisp/*" :directories-are-files nil))
>     (when (excl:file-directory-p dir-candidate)
>       (let ((asd-candidate (merge-pathnames "*.asd" dir-candidate)))
>         (when (directory asd-candidate)
>           (push dir-candidate asdf:*central-registry*)))))
>
> That should slurp in all "c:/home/lisp/*/*.asd" system definitions.
>
> > That was all the testing I can do. BTW: the CL+SSL problems I
> > experienced were with the newest clisp (2.41), so it looks like
> > Drakma isn't able to run on clisp anymore (?).
>
> Hmm, maybe the CLISP users on this list should try and report to the

Re: Portability of Drakma

On Sat, 7 Apr 2007 00:13:28 +0200, "Erik Huelsmann" <ehuels <at> gmail.com> wrote:

> I'm not aware of a public Drakma repository.

There isn't any.

> If there isn't, could you tell me whether you applied the patch
> if/when you do? I can update the Drakma item in the cl-directory
> then.

Sorry for asking dumb questions, but did you send the patch already?
When was that?

> Thank you too, for all the libraries you provide!

You're welcome... :)

Re: Portability of Drakma

On 4/7/07, Edi Weitz <edi <at> agharta.de> wrote:
> On Sat, 7 Apr 2007 00:13:28 +0200, "Erik Huelsmann" <ehuels <at> gmail.com> wrote:
>
> > I'm not aware of a public Drakma repository.
>
> There isn't any.
>
> > If there isn't, could you tell me whether you applied the patch
> > if/when you do? I can update the Drakma item in the cl-directory
> > then.
>
> Sorry for asking dumb questions, but did you send the patch already?
> When was that?

In a message on March 5th, I sent a message which included a reference
to a patch located on the net and also an archive based on
drakma-0.6.0, with the patch built in. (http://hix.nu/drakma/)

For your convenience, I attached the patch to this message too. I see
that you have released 0.6.2 now, but the patch still seems to apply
just fine. It updates doc/index.html, drakma.asd and request.lisp.

bye,

Erik.

_______________________________________________
drakma-devel mailing list

[ann] [drakma-announce] New release 0.7.0 (Was: Portability of Drakma)

On Sat, 7 Apr 2007 16:52:40 +0200, "Erik Huelsmann"
<ehuels@...> wrote:

> For your convenience, I attached the patch to this message too.

OK, thanks, I've now made a new release (0.7.0) based on your patch.

Cheers,
Edi.
_______________________________________________
drakma-announce mailing list
drakma-announce@...
http://common-lisp.net/cgi-bin/mailman/listinfo/drakma-announce
_______________________________________________
announcements site list
announcements@...
http://common-lisp.net/mailman/listinfo/announcements

Re: Portability of Drakma

On Sat, 7 Apr 2007 16:52:40 +0200, "Erik Huelsmann" <ehuels <at> gmail.com> wrote:

> For your convenience, I attached the patch to this message too.

As the docs point to the CLiki page and say 0.3.2 or higher is
required, it'd be nice if the CLiki page pointed to something like
0.3.2 (or higher) - also for ASDF-INSTALL.