all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Add guile-minikanren
Date: Thu, 23 Apr 2015 15:44:51 +0200	[thread overview]
Message-ID: <87zj5zot64.fsf@taylan.uni.cx> (raw)
In-Reply-To: <20150423131751.GA12941@debian.math.u-bordeaux1.fr> (Andreas Enge's message of "Thu, 23 Apr 2015 15:17:51 +0200")

Andreas Enge <andreas@enge.fr> writes:

>> I named it guile-minikanren which isn't really accurate.  I'm not sure
>> how else I could name it though?  I'd be open to suggestions!
>
> There is a chapter in the documentation about this:
>    https://www.gnu.org/software/guix/manual/guix.html#Package-Naming
> The main idea is to not think too much, but to simply use the upstream
> project name. Here this seems to be "minikanren" without "guile-".
> We have special rules for perl and python; maybe we also need a special
> rule for guile?

I think the issue here is that miniKanren is a project of its own, and
this is a Guile port by a third party, so the package probably shouldn't
squat the name "minikanren".

IMO "guile-foo" is sensible for packages that install a Guile module,
akin to "perl-foo" and "python-foo".

Taylan

  reply	other threads:[~2015-04-23 13:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 15:15 Add guile-minikanren Christopher Allan Webber
2015-04-23 13:17 ` Andreas Enge
2015-04-23 13:44   ` Taylan Ulrich Bayırlı/Kammer [this message]
2015-04-23 13:46   ` Thompson, David
2015-04-23 13:52     ` Andreas Enge
2015-04-23 18:57     ` Ludovic Courtès
2015-04-23 19:48       ` Eric Bavier
2015-04-23 19:51         ` Andreas Enge
2015-04-23 21:10         ` Ludovic Courtès
2015-04-24  2:46     ` Christopher Allan Webber
2015-04-25 21:30       ` Christopher Allan Webber
2015-04-27  1:46         ` David Thompson

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=87zj5zot64.fsf@taylan.uni.cx \
    --to=taylanbayirli@gmail.com \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    /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.