unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "jgart" <jgart@dismail.de>
To: guix-devel@gnu.org
Cc: glv@posteo.net, "Charles" <charles.b.jackson@protonmail.com>,
	contact@conses.eu
Subject: Should Guix support writing CLI Common Lisp scripts? (Think Roswell)
Date: Tue, 27 Dec 2022 18:14:55 +0000	[thread overview]
Message-ID: <24871675f2ccdf7f3c46c46832b3f3f9@dismail.de> (raw)

Hi Guixers,

Should Guix support writing CLI Common Lisp scripts? (Think Roswell)

> Although Roswell is a unified interface to Common Lisp implementations, it also encourages writing scripts with it.
> A "Roswell script" is an implementation-independent script which can be invoked from a shell command line, launched by > Roswell and run under standard CL environment.

Just insert "Guix" wherever you see Roswell mentioned in the above quote.

> * A roswell script can be distributed using quicklisp's infrastructure

Just insert "Guix" wherever you see quicklisp is mentioned in the above quote.

> If you're the author of the library, then consider adding the ros file to the repository and automatically providing a roswell-installable command-line interface to it.

Same above, insert Guix.

I think we should make it easier for Lispers to write CLI scripts with Guix.

WDYT

https://roswell.github.io/Roswell-as-a-Scripting-Environment.html


             reply	other threads:[~2022-12-27 18:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27 18:14 jgart [this message]
2022-12-27 18:25 ` Should Guix support writing CLI Common Lisp scripts? (Think Roswell) John Kehayias
2023-01-16  1:01   ` Charles
2022-12-27 19:23 ` jgart
2022-12-27 19:58   ` Russell Sim
2022-12-27 21:06   ` jgart
2022-12-27 21:42     ` Russell Sim
2023-01-17 10:07       ` Attila Lendvai
2022-12-27 22:06   ` bokr

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=24871675f2ccdf7f3c46c46832b3f3f9@dismail.de \
    --to=jgart@dismail.de \
    --cc=charles.b.jackson@protonmail.com \
    --cc=contact@conses.eu \
    --cc=glv@posteo.net \
    --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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).