all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Andy Patterson <ajpatter@uwaterloo.ca>
Cc: 32769@debbugs.gnu.org
Subject: bug#32769: Packaging Next browser (Common Lisp) [work in progress]
Date: Mon, 15 Oct 2018 11:34:14 +0200	[thread overview]
Message-ID: <87o9bvk0yx.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20181015020505.2387a8c7@mailservices.uwaterloo.ca>

[-- Attachment #1: Type: text/plain, Size: 677 bytes --]

Hi Andy!

Thanks for the hard work, this is pretty elegant indeed!

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?

> I wasn't able to really test whether or not it works - it throws an
> exception whenever I press a key.

Same here.  It does not do that when built manually with Quicklisp.  Although I
recall seeing something similar when building manually with the wrong arguments.

I also suspect that some CFFI dependency (gtk?) is not packaged correctly and
some paths are missing.

I'll look into it.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2018-10-15  9:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  7:15 bug#32769: Packaging Next browser (Common Lisp) [work in progress] Pierre Neidhardt
2018-10-10 13:21 ` Pierre Neidhardt
2018-10-11  7:16   ` Andy Patterson
2018-10-11  8:50     ` Pierre Neidhardt
2018-10-11 10:44       ` Pierre Neidhardt
2018-10-12  5:51         ` Andy Patterson
2018-10-12  6:44           ` Pierre Neidhardt
2018-10-12 22:25             ` Andy Patterson
2018-10-14  8:27               ` Pierre Neidhardt
2018-10-15  6:05                 ` Andy Patterson
2018-10-15  9:34                   ` Pierre Neidhardt [this message]
2018-10-15 10:04                     ` Pierre Neidhardt
2018-10-16  3:11                     ` Andy Patterson
2018-10-19 16:05                       ` Pierre Neidhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o9bvk0yx.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=32769@debbugs.gnu.org \
    --cc=ajpatter@uwaterloo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.