all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andy Patterson <ajpatter@uwaterloo.ca>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Lisp: Package cl-cffi-gtk
Date: Thu, 11 Oct 2018 03:30:26 -0400	[thread overview]
Message-ID: <20181011033026.65950dce@mailservices.uwaterloo.ca> (raw)
In-Reply-To: <87woqq7xhq.fsf@ambrevar.xyz>

Hi,

On Wed, 10 Oct 2018 15:16:33 +0200
Pierre Neidhardt <mail@ambrevar.xyz> wrote:

> Alright, I've packaged it as you suggested.  See the wip-nextbrowser
> branch. If was slightly simpler as for Sly.
> 
> That said, I wonder if this is not over-complicated.
> Wouldn't it be easier to mimic Quicklisp there and automatically push
> all .asd to the central registry?  

We don't want to use the central registry at all as it's the older way
to tell asdf where systems live, and it's less flexible.  I understand
what you're getting at though.  I do think there are some advantages to
mapping systems to packages.  It allows the guix dependency graph to
exactly match the real dependency graph between systems, for example.
The #:asd-system-name and #:asd-file arguments could become complicated
if we're going to support multiple systems per package.

If you feel that it's worth it to do this, I could have a go at
implementing it so that we can see what it would look like (I might do
this anyway).  Of course, you're also free to do so as well, and I can
help if you need.

--
Andy

  reply	other threads:[~2018-10-11  7:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 19:41 Lisp: Package cl-cffi-gtk Pierre Neidhardt
2018-10-10  5:51 ` Andy Patterson
2018-10-10 13:16   ` Pierre Neidhardt
2018-10-11  7:30     ` Andy Patterson [this message]
2018-10-11  8:48       ` 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=20181011033026.65950dce@mailservices.uwaterloo.ca \
    --to=ajpatter@uwaterloo.ca \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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.