Re: ActtivityPub and Haunt

[Christine Lemmer-Webber]

indieterminacy  writes:

> As can be imagined, some of these softwares have stacks which Guix is
> not so usually adept at packaging.

As a side note, I suspect the major paint point of *all* of these
systems, which is the Javascript side for user-facing interface stuff,
can at last have a path out we can help contribute to without needing to
untangle NPM and friends: Spritely's Hoot project should allow us to
deliver browser-side scheme execution very soon!

That will make Guile a *much* more interesting target for web
development :)

 - Christine

Re: Help Packaging Incudine (Common Lisp)

[Théo Tyburn]

Liliana Marie Prikler  writes:

> Am Donnerstag, dem 28.09.2023 um 12:23 + schrieb Théo Tyburn:
>> Oh, it seems I took the WARNING message for an ERROR message.
>> 
>> The error message seems to just be:
>> > Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #> > THREAD:THREAD tid=21 "main thread" RUNNING
>> > 
>> > {100AFE8113}>:
>> >  COMPILE-FILE-ERROR while
>> >  compiling #
>> 
>> No sure what can be done with this.
> Note that this error doesn't tell you where CL would have written the
> compiled file to.
>
> Am Donnerstag, dem 28.09.2023 um 14:21 + schrieb Théo Tyburn:
>> Not sure in what retrying a compilation on the interactive debugger
>> is different from compiling normally. But I need to understand why
>> the retrying of compilation does in order to replicate it without the
>> need of an interactive session.
> I'd hazard a guess that your $HOME is writable in the interactive case
> and not so much during guix build :)
> Well, that still doesn't explain why the compilation fails normally in
> the interactive case, does it?  I think for that you'd have to look up
> uiop/lisp-build:compile-file and see when it raises errors.  Enter
> rubber ducky.

Yes, that's probably the right place to look for hints. Need to find out
where and how compiled files are written.

Thanks