From: "Ludovic Courtès" <ludo@gnu.org>
To: Philip McGrath <philip@philipmcgrath.com>
Cc: 49280@debbugs.gnu.org
Subject: [bug#49280] [PATCH 0/4] gnu: racket: Add racket-next. Bootstrap from C.
Date: Thu, 08 Jul 2021 23:25:42 +0200 [thread overview]
Message-ID: <87lf6gjy5l.fsf_-_@gnu.org> (raw)
In-Reply-To: <20210629215742.3112654-2-philip@philipmcgrath.com> (Philip McGrath's message of "Tue, 29 Jun 2021 17:57:40 -0400")
Hi!
Philip McGrath <philip@philipmcgrath.com> skribis:
> * gnu/packages/racket.scm (racket-next-minimal,racket-next): New variables.
[...]
> +++ b/gnu/packages/racket.scm
> @@ -23,6 +23,7 @@
> #:use-module ((guix licenses)
> #:select (asl2.0 expat lgpl3+))
> #:use-module (guix packages)
> + #:use-module (guix base16)
Leftover?
> +;; Preliminary guidelines on naming things:
> +;; - `racket` is the main package. It corresponds to `racket-minimal`
> +;; with the Racket-level package "main-distribution" installed.
> +;; - `racket-minimal` is Racket runtime system and core libraries:
> +;; just enough to implement the package system and install the rest.
> +;; Upstream refers to this as "minimal Racket".
Note that these two names match existing conventions in Guix.
I’d suggest moving the bits about the package contents/features next to
the definition of ‘racket’ and ‘racket-minimal’.
> +;; - `racket-pkg-` should probably be the prefix for Racket packages
> +;; available as Guix packages, once we're able to build those.
> +;; More specifically, it should correspond
> +;; to packages registered in the catalog at https://pkgs.rackat-lang.org.
> +;; This is a social convention to manage the namespace, not a technical
> +;; limitation: Racket can use other catalogs (e.g. for pre-built packages
> +;; or packages pinned to specific versions), unregistered package source
> +;; urls, or purely local packages. But we also need a convention to
> +;; manage the namespace, so we should use this one. In practice,
> +;; all generally useful libre Racket packages are registered there.
> +;; We probably will need a clever encoding scheme to deal with the fact
> +;; that Racket package names can contain [A-Za-z_-], i.e. including "_",
> +;; which is not allowed in Guix package names.
For this there’s already a documented convention (info "(guix) Package
Naming"), although part of it is undocumented. The prefix would rather
be “racket-” to match what we do with other packages–“ghc-”, “ocaml-”,
“guile-”, and so forth.
> +;; - `racket-next` is a development version of `racket`, following either
> +;; the upstrean Git HEAD or the release candidate, when one exists.
> +;; - `racket-next-` is the prefix for other development packages,
> +;; including `racket-next-minimal`. When we can build Racket packages
> +;; individually, we will need `racket-next-pkg-` for the packages
> +;; that make up `racket-next`.
These two are also conventional and don’t need to be documented here
IMO.
> +(define %pre-release-installers
> + "https://pre-release.racket-lang.org/installers/")
> +
> +(define-public racket-next-minimal
> + (package
> + (inherit racket-minimal)
> + (name "racket-next-minimal")
> + (version "8.1.900")
> + (source
> + (origin
> + (inherit (package-source racket-minimal))
> + (sha256
> + (base32
> + "0dm849wvlaxpfgz2qmgy2kwdslyi515rxn1m1yff38lagbn21vxq"))
> + (uri (string-append %pre-release-installers
> + "racket-minimal-src.tgz"))))))
> +
> +(define-public racket-next
> + (package
> + (inherit racket)
> + (name "racket-next")
> + (version (package-version racket-next-minimal))
> + (source
> + (origin
> + (inherit (package-source racket))
> + (sha256
> + (base32
> + "0ysvzgm0lx4b1p4k9balvcbvh2kapbfx91c9ls80ba062cd8y5qv"))
> + (uri (string-append %pre-release-installers
> + "racket-src.tgz"))))))
Do I get it right that *-src.tgz are not versioned? That they’re
updated in place regularly?
In that case, we cannot refer to them in a package definition since the
hash is bound to become stale.
What we could do is refer to, say,
<https://pre-release.racket-lang.org/installers/racket-8.1.900.1-src.tgz>.
However, I suspect this file would vanish fairly quickly from the web
site, which is not okay either.
I’m not sure what a good solution would be. WDYT?
It may be that
‘--with-source=https://pre-release.racket-lang.org/installers/racket-src.tgz’
would do the job for those who’re into that.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-07-08 21:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 21:52 [bug#49280] [PATCH 0/4] gnu: racket: Add racket-next. Bootstrap from C Philip McGrath
2021-06-29 21:57 ` [bug#49280] [PATCH 1/4] gnu: racket: Fix lib-search-dirs configuration Philip McGrath
2021-06-29 21:57 ` [bug#49280] [PATCH 2/4] gnu: racket: Add racket-next and racket-next-minimal Philip McGrath
2021-07-08 21:25 ` Ludovic Courtès [this message]
2021-07-18 21:35 ` [bug#49280] [PATCH 0/4] gnu: racket: Add racket-next. Bootstrap from C Philip McGrath
2021-07-19 6:31 ` [bug#49280] [PATCH v2 1/3] gnu: racket: Update to 8.2 Philip McGrath
2021-07-19 6:31 ` [bug#49280] [PATCH v2 2/3] gnu: racket: Unbundle racket-minimal Philip McGrath
2021-07-30 21:33 ` [bug#49280] [PATCH v2 0/3] gnu: racket: Update to 8.2. Bootstrap from C Ludovic Courtès
2021-07-19 6:31 ` [bug#49280] [PATCH v2 3/3] gnu: racket-minimal: " Philip McGrath
2021-07-19 18:48 ` Philip McGrath
2021-07-19 19:46 ` [bug#49280] [PATCH v2 1/3] gnu: racket: Update to 8.2 Leo Prikler
2021-07-19 21:46 ` Philip McGrath
2021-07-20 9:40 ` Leo Prikler
2021-07-25 8:22 ` Philip McGrath
2021-07-25 13:03 ` Leo Prikler
2021-07-25 18:04 ` Philip McGrath
2021-07-30 23:05 ` bug#49280: [PATCH v2 0/3] gnu: racket: Update to 8.2. Bootstrap from C Ludovic Courtès
2021-07-30 21:22 ` [bug#49280] " Ludovic Courtès
2021-07-30 21:31 ` [bug#49280] References to unversioned source tarballs Ludovic Courtès
2021-07-30 22:08 ` Philip McGrath
2021-06-29 21:57 ` [bug#49280] [PATCH 3/4] gnu: racket-next: Unbundle racket-next-minimal Philip McGrath
2021-06-29 21:57 ` [bug#49280] [PATCH 4/4] gnu: racket-next-minimal: Bootstrap from C Philip McGrath
2021-07-08 21:43 ` [bug#49280] [PATCH 0/4] gnu: racket: Add racket-next. " Ludovic Courtès
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=87lf6gjy5l.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=49280@debbugs.gnu.org \
--cc=philip@philipmcgrath.com \
/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).