bug#32770: Packaging SLIME/SWANK as Common Lisp library

2019-10-06 Thread Pierre Neidhardt
Fixed with 2026204a13515aaa9b7814f9a6f0a60b65493bd1. -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

bug#32770: Packaging SLIME/SWANK as Common Lisp library

2018-10-09 Thread Andy Patterson
Hi Pierre, On Fri, 05 Oct 2018 15:30:03 +0200 Pierre Neidhardt wrote: > > In “guile-sly”, for example, the configure script accepts > > “--with-libfreeimage-prefix=” and “--with-libgslcblas-prefix=”, > > which are then used to construct a full path to the libraries. In > > other cases where the

bug#32770: Packaging SLIME/SWANK as Common Lisp library

2018-10-05 Thread Ricardo Wurmus
Hi, >> Adding to *foreign-library-directories* at compile time may allow a >> package to compile, but I get the feeling that it may not have the >> desired effect when you try to load the package later on. > > Why? In my experience it works for a compiled Next executable. > >> I guess another app

bug#32770: Packaging SLIME/SWANK as Common Lisp library

2018-10-05 Thread Ricardo Wurmus
Pierre Neidhardt writes: >> What I'm >> thinking of is something like a configure script to set the library >> paths before building is done. I think there are some examples of >> guile projects which do just that. > > Hmm, I'm not sure I understand what you mean. Could you provide an example

bug#32770: Packaging SLIME/SWANK as Common Lisp library

2018-10-04 Thread Andy Patterson
Hi Pierre, I've seen your later e-mail but I'd still like to answer some of your questions here. On Thu, 04 Oct 2018 10:37:08 +0200 Pierre Neidhardt wrote: > CC-ing Ludovic and Ricardo if they want to chime in. > > Thanks for the feedback, Andy, so invaluable as always. > > > I've been using

bug#32770: Packaging SLIME/SWANK as Common Lisp library

2018-10-04 Thread Pierre Neidhardt
CC-ing Ludovic and Ricardo if they want to chime in. Thanks for the feedback, Andy, so invaluable as always. > I've been using a cffi consumer for a while now, and my approach for > that package was to update references to library and header files with > the full paths to their respective store i

bug#32770: Packaging SLIME/SWANK as Common Lisp library

2018-10-03 Thread Andy Patterson
Hi, On Wed, 03 Oct 2018 20:34:24 +0200 Pierre Neidhardt wrote: > Last (hopefully?) step before getting Next up and running: add > support for CFFI. > > I've re-used your CFFI package and they seem to work. Now if I want > to package cl-sqlite, it fails because sqlite.so cannot be found. > Inde

bug#32770: Packaging SLIME/SWANK as Common Lisp library

2018-10-03 Thread Pierre Neidhardt
Hmmm, I should have posted this on Next's bug, not this one, sorry. -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

bug#32770: Packaging SLIME/SWANK as Common Lisp library

2018-10-02 Thread Andy Patterson
Hi Pierre, On Tue, 02 Oct 2018 12:24:29 +0200 Pierre Neidhardt wrote: > > It'd be nice to have an importer. Maybe we can use Nix's work to > > reduce the amount of investigation needed to get there. > > Absolutely. ASDF is good enough that the vast majority of CL > libraries can be packaged

bug#32770: Packaging SLIME/SWANK as Common Lisp library

2018-10-02 Thread Pierre Neidhardt
> It'd be nice to have an importer. Maybe we can use Nix's work to > reduce the amount of investigation needed to get there. Absolutely. ASDF is good enough that the vast majority of CL libraries can be packaged without an itch. If we could use Quicklisp or http://quickdocs.org/ to

bug#32770: Packaging SLIME/SWANK as Common Lisp library

2018-10-02 Thread Andy Patterson
Hi, On Sun, 30 Sep 2018 23:46:08 +0200 Pierre Neidhardt wrote: > Also see > > https://github.com/quicklisp/quicklisp-projects/issues/1561 > > There are some interesting links, mostly about the Nix system. See > the > > > https://github.com/NixOS/nixpkgs/blob/5048b0d1f9e908665a01

bug#32770: Packaging SLIME/SWANK as Common Lisp library

2018-10-02 Thread Andy Patterson
Hi, On Mon, 01 Oct 2018 15:53:50 +0200 Pierre Neidhardt wrote: > Another issue, Andy, is with the new `normalize-dependency' function > that adds support for the dependency syntax as specified by the ASDF > grammar. I think your approach is good but it fails for `jpl-queues` > because it produc

bug#32770: Packaging SLIME/SWANK as Common Lisp library

2018-10-01 Thread Pierre Neidhardt
Another issue, Andy, is with the new `normalize-dependency' function that adds support for the dependency syntax as specified by the ASDF grammar. I think your approach is good but it fails for `jpl-queues` because it produces the following .asd file in the store: --8<---cut here-

bug#32770: Packaging SLIME/SWANK as Common Lisp library

2018-09-29 Thread Andy Patterson
Hey Pierre, Sorry for taking so long to get back to you. On Wed, 19 Sep 2018 09:19:46 +0200 Pierre Neidhardt wrote: > On the long road to packaging Next browser (bug #32729), I've hit a > big obstacle: packaging the SLIME/SWANK dependency. > > We currently have an emacs-slime package, but that