bug#32769: Packaging Next browser (Common Lisp) [work in progress]

2018-10-19 Thread Pierre Neidhardt
I haven't managed to figure what's happening. According to John Mercouris (Next developer), the state of CFFI-GTK is rather poor and it will be hard to track down exactly what's wrong. Next browser will soon move to another interface which does not rely on cffi-gtk so it won't be a problem. Andy

bug#32769: Packaging Next browser (Common Lisp) [work in progress]

2018-10-15 Thread Andy Patterson
Hi Pierre, On Mon, 15 Oct 2018 11:34:14 +0200 Pierre Neidhardt wrote: > Question: do we need both "out" and "lib" outputs? > My understanding is that "lib" is useful when one wants to start the > program from a REPL. Correct? "out" will always depend on "lib" for programs. We want to build it

bug#32769: Packaging Next browser (Common Lisp) [work in progress]

2018-10-15 Thread Pierre Neidhardt
It could also be a dependency version that's different from the one pulled by Quicklisp. -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

bug#32769: Packaging Next browser (Common Lisp) [work in progress]

2018-10-14 Thread Andy Patterson
Hi Pierre, On Sun, 14 Oct 2018 10:27:46 +0200 Pierre Neidhardt wrote: > I won't have time this weekend, so you can go ahead. Otherwise I'll > do it next week. I investigated the problem and I think the build-program procedure is ok. It has the option to specify which dependencies you want (ma

bug#32769: Packaging Next browser (Common Lisp) [work in progress]

2018-10-12 Thread Andy Patterson
Hi, On Fri, 12 Oct 2018 08:44:35 +0200 Pierre Neidhardt wrote: > Let me know if you'd like to do it or if I should give it a shot :) > Please feel free. I'll probably get around to it this weekend if you don't have time before then, if that's ok with you. Thanks, -- Andy

bug#32769: Packaging Next browser (Common Lisp) [work in progress]

2018-10-11 Thread Pierre Neidhardt
Let me know if you'd like to do it or if I should give it a shot :) -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

bug#32769: Packaging Next browser (Common Lisp) [work in progress]

2018-10-11 Thread Andy Patterson
Hi Pierre, On Thu, 11 Oct 2018 12:44:43 +0200 Pierre Neidhardt wrote: > You were right, this was the issue. I've posted a patch upstream, it > should be fixed soon. > > Now Next compiles. Hurray!!! :D Nice. > > There is one last step though: the .asd bunble works, but not the > "build-prog

bug#32769: Packaging Next browser (Common Lisp) [work in progress]

2018-10-11 Thread Andy Patterson
Hi, On Wed, 10 Oct 2018 15:21:26 +0200 Pierre Neidhardt wrote: > The good news: all Next browser dependencies are now packaged under > the branch wip-nextbrowser. > > The bad news: Next browser fails to build. > > [...] > > Andy, any clue on this? It's probably the > ; caught WARNING: > ;

bug#32769: Packaging Next browser (Common Lisp) [work in progress]

2018-10-10 Thread Pierre Neidhardt
The good news: all Next browser dependencies are now packaged under the branch wip-nextbrowser. The bad news: Next browser fails to build. --8<---cut here---start->8--- ; compiling file "/gnu/store/39vh5ghdn9x7zwb6ky7law678wkz20l2-next-browser-0.0.8-1.ccc289b/

bug#32769: Packaging Next browser (Common Lisp) [work in progress]

2018-09-19 Thread Pierre Neidhardt
I've started working on packaging a collection of Common Lisp dependencies for Next browser: http://next.atlas.engineer/ My progress can be found on the wip-next-browser branch. -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature