[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#42690] add sbcl-cl-lambda-fiddle

From: Brett Gilio
Subject: [bug#42690] add sbcl-cl-lambda-fiddle
Date: Mon, 03 Aug 2020 23:21:09 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)

Adam Kandur <> writes:

> (define-public sbcl-cl-lambda-fiddle
>   (let ((commit "d16bba55acf6065b412f64ab8fdff679a4a32b1e")
> (revision "1"))
>     (package
>       (name "sbcl-lambda-fiddle")
>       (version (git-version "0.0.0" revision commit))
>       (source
>        (origin
>          (method git-fetch)
>          (uri (git-reference
>                (url "";)
>                (commit commit)))
>          (file-name (git-file-name name version))
>          (sha256
>           (base32 "1zarj1pqjqmk95kdx1axkgpwy2wq3canczk7f9z5hvaw5an6gand"))))
>       (build-system asdf-build-system/sbcl)
>       (home-page "";)
>       (synopsis "Lambda-fiddle is a collection of utilities to process 
> lambda-lists.")
>       (description "Lambda-fiddle is a collection of utilities to process 
> lambda-lists.
> Mostly useful in contexts where you want a macro that uses lambda-lists in 
> some fashion but need more precise processing.")
>       (license license:zlib))))

Hi Adam,

Thank you for your submission. A few issues before we can proceed.

1. You have what I believe is a naming error (the cl in the name
probably should not be there, as we have a different purpose for cl-*
named packages).

2. The synopsis should not include the package name, and should not be
too close to the package description. See our packaging guidelines:

3. Guix accepts pcontributions in the form of git patches, which give us
the extra metadata to be able to easily apply your contribution to our
git tree (and ensure you get the proper credit for your work!). Also
taking care to add yourself to the copyright header if not already
there. Please see our documentation on submitting git patches:

Once we get these in order, we can merge your work!


Brett Gilio

reply via email to

[Prev in Thread] Current Thread [Next in Thread]