all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: jgart via Guix-patches via <guix-patches@gnu.org>
To: Charles <charles.b.jackson@protonmail.com>
Cc: glv@posteo.net, paren@disroot.org, 59052@debbugs.gnu.org
Subject: [bug#59052] [PATCH] gnu: sbcl-triads: Install binary executable.
Date: Sun, 6 Nov 2022 11:24:21 -0600	[thread overview]
Message-ID: <20221106112421.GB14752@dismail.de> (raw)
In-Reply-To: <qAGmQLLXm11C8aays2eLfN_F997v-xQ1eMy-1VV-0e5d3dhTmWyKlip74DO9fSMwPCWWnMeFFX7ty8jbe8_yu797W8pfoHBrM9uFNShjPKM=@protonmail.com>

On Sat, 05 Nov 2022 19:21:43 +0000 Charles <charles.b.jackson@protonmail.com> wrote:
> > On Sat Nov 5, 2022 at 7:15 PM GMT, Charles via Guix-patches via wrote: > My personal thought is that there should be the 3 *cl-triads in lisp-xyz.scm and then a triads in music.scm that is installs a binary. I'm not sure what guix standard is about this. How about an output; ``cl-triads:bin''? -- (

> I'm not sure what guix standard is about this.

Hi, how would we like to proceed?

I'm fine with either approach. Charles, would you like to send an update
patch for your approach? I might need about a weekish to get back to this.




  reply	other threads:[~2022-11-06 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05 14:49 [bug#59052] [PATCH] gnu: sbcl-triads: Install binary executable jgart via Guix-patches via
2022-11-05 19:02 ` Guillaume Le Vaillant
2022-11-05 19:15   ` Charles via Guix-patches via
2022-11-05 19:17     ` ( via Guix-patches via
2022-11-05 19:21       ` Charles via Guix-patches via
2022-11-06 17:24         ` jgart via Guix-patches via [this message]
2022-12-14  5:06 ` [bug#59052] Add sbcl-triads:bin patch Charles via Guix-patches via
2022-12-19 13:25   ` bug#59052: " Guillaume Le Vaillant

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=20221106112421.GB14752@dismail.de \
    --to=guix-patches@gnu.org \
    --cc=59052@debbugs.gnu.org \
    --cc=charles.b.jackson@protonmail.com \
    --cc=glv@posteo.net \
    --cc=jgart@dismail.de \
    --cc=paren@disroot.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.