[bug#71202] gnu: lisp.scm: add roswell package

[bug#71202] gnu: lisp.scm: add roswell package

[not emma via Guix-patches via]

[-- Attachment #1.1: Type: text/plain, Size: 243 bytes --]

I was unsure whether this would fit better under lisp.scm, or lisp-xyz.scm, but think the former is a better choice because it's independent of any specific common lisp implementation.

Sent with [Proton Mail](https://proton.me/) secure email.

[-- Attachment #1.2: Type: text/html, Size: 751 bytes --]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: roswell-diff.scm --]
[-- Type: text/x-scheme; name=roswell-diff.scm, Size: 2590 bytes --]

diff --git a/gnu/packages/lisp.scm b/gnu/packages/lisp.scm
index 83ff93719e..f50284fdeb 100644
--- a/gnu/packages/lisp.scm
+++ b/gnu/packages/lisp.scm
@@ -27,6 +27,7 @@
 ;;; Copyright © 2023 Yovan Naumovski <yovan@gorski.stream>
 ;;; Copyright © 2023 Andrew Kravchuk <awkravchuk@gmail.com>
 ;;; Copyright © 2024 Andreas Enge <andreas@enge.fr>
+;;; Copyright © 2024 bigbug <bigbookofbug@proton.me>
 ;;;
 ;;; This file is part of GNU Guix.
 ;;;
@@ -62,12 +63,15 @@ (define-module (gnu packages lisp)
   #:use-module (guix build-system trivial)
   #:use-module (gnu packages admin)
   #:use-module (gnu packages algebra)
+  #:use-module (gnu packages autotools)
   #:use-module (gnu packages base)
   #:use-module (gnu packages bash)
   #:use-module (gnu packages bdw-gc)
   #:use-module (gnu packages check)
   #:use-module (gnu packages compression)
+  #:use-module (gnu packages curl)
   #:use-module (gnu packages dbm)
+  #:use-module (gnu packages elf)
   #:use-module (gnu packages fontutils)
   #:use-module (gnu packages gcc)
   #:use-module (gnu packages gettext)
@@ -1614,3 +1618,37 @@ (define-public s7
                 (delete-file (string-append #$output "/bin/ffitest"))))))))
     (native-inputs (list s7-bootstrap))
     (properties (alist-delete 'hidden? (package-properties s7-bootstrap)))))
+
+(define-public roswell
+  (package
+   (name "roswell")
+   (version "23.10.14.114")
+   (home-page "https://github.com/roswell/roswell")
+   (source
+    (origin
+     (method git-fetch)
+     (uri (git-reference
+	   (url "https://github.com/roswell/roswell")
+	   (commit (string-append "v" version))))
+     (sha256
+      (base32 "05w5sjh1bfy2wnblc09cb9qs8h7hxkx5hcqlbgpn7md32b0m4h7g"))))
+   (build-system gnu-build-system)
+   (arguments
+    `(#:configure-flags (list (string-append "--prefix=" %output))
+      #:tests? #f))
+   (native-inputs
+    (list automake autoconf intltool))
+   (inputs (list curl))
+   (propagated-inputs (list patchelf gnu-make)) ;;has to be propogated in order to be found during setup
+   (synopsis "Common Lisp implementation manager, launcher, and more")
+   (description
+    "Roswell started out as a command-line tool with the aim to make
+installing and managing Common Lisp implementations really simple and easy.
+Roswell has now evolved into a full-stack environment for Common Lisp
+development, and has many features that makes it easy to test, share, and
+distribute your Lisp applications.
+
+Roswell is still in beta. Despite this, the basic interfaces are stable and
+not likely to change.")
+   (license license:expat)))

[bug#71202] gnu: lisp.scm: add roswell package

[Guillaume Le Vaillant]

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

Hi.

I remember that in the past someone tried to make a patch for roswell.
It built fine, but there were some issues when running it. Roswell
had difficulties finding or running sbcl, I think.

So, with your patch, does everything just work fine when building and
running it?
Or are there some extra configuration steps to take? If so, maybe it
could be indicated in the 'description' field.

See <https://issues.guix.gnu.org/37200>
and <https://github.com/roswell/roswell/issues/387>.

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

[bug#71202] gnu: lisp.scm: add roswell package

[not emma via Guix-patches via]

Hi,

I had some initial issues with sbcl and glibc32, but those were resolved by propagating patchelf and make (the former to resolve the glibc32 error, and the latter because roswell has to run a setup on initial install, and references its makefile). Based on this issue: https://github.com/roswell/roswell/issues/387 , it seems like the primary difficulty was with curl, but that was resolved. 




Sent with Proton Mail secure email.

On Monday, May 27th, 2024 at 12:03 PM, Guillaume Le Vaillant <glv@posteo.net> wrote:

> Hi.
> 
> I remember that in the past someone tried to make a patch for roswell.
> It built fine, but there were some issues when running it. Roswell
> had difficulties finding or running sbcl, I think.
> 
> So, with your patch, does everything just work fine when building and
> running it?
> Or are there some extra configuration steps to take? If so, maybe it
> could be indicated in the 'description' field.
> 
> See https://issues.guix.gnu.org/37200
> 
> and https://github.com/roswell/roswell/issues/387.

bug#71202: gnu: lisp.scm: add roswell package

[Guillaume Le Vaillant]

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

Patch applied as 542b18709a46e361de8f25e3fece29860532743c with a few
modifications.
Thanks.

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