From: Sarah Morgensen <iskarian@mgsn.dev>
To: guix-devel@gnu.org
Subject: Can we find a better idiom for unversioned packages?
Date: Tue, 31 Aug 2021 12:57:23 -0700 [thread overview]
Message-ID: <8635qp1j6k.fsf@mgsn.dev> (raw)
Hello Guix,
Currently, there are about 1500 packages defined like this:
--8<---------------cut here---------------start------------->8---
(define-public sbcl-feeder
(let ((commit "b05f517d7729564575cc809e086c262646a94d34")
(revision "1"))
(package
[...])))
--8<---------------cut here---------------end--------------->8---
I feel like there are some issues with this idiom (in no particular
order):
1. When converting between this idiom and regularly versioned packages,
the git diff shows the whole package changing because of the indentation
change.
2. We cannot get at the source location for the definition of 'commit' or
'revision'. This would be useful for updating these packages with `guix
refresh -u`. There is a proposed patch [0] to work around this, but it
*is* a workaround.
3. Packages inheriting from it lose the definitions. For actual fields,
we have e.g. `(package-version this-package)`, but we have no equivalent
for these.
4. Horizontal space is at a premium, and an extra two spaces here and
there add up. (Personally, I think we could do with a
define-public-package macro to save another two spaces, but that's for
another day...)
5. The closest thing we have to a standardized way of generating
versions for these packages is `(version (git-version "0.0.0" revision
commit))`. We can do better than that boilerplate.
6. Not a direct complaint, but I feel like the overall package interface
was designed before straight-from-vcs unversioned packages were so
common, and so this idiom developed organically to work around that.
I do not have a specific solution in mind, but I think there must be
one. I do have a few half-baked ideas, but I'm curious what we can all
come up with together. Or maybe you'll just tell me I'm just being
awfully picky :)
[0] https://issues.guix.gnu.org/50286
--
Sarah
next reply other threads:[~2021-08-31 19:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 19:57 Sarah Morgensen [this message]
2021-08-31 21:20 ` Can we find a better idiom for unversioned packages? Maxime Devos
2021-09-01 12:11 ` Xinglu Chen
2021-09-01 16:29 ` Maxime Devos
2021-09-01 13:33 ` Liliana Marie Prikler
2021-09-01 16:39 ` Maxime Devos
2021-09-01 18:34 ` Liliana Marie Prikler
2021-09-02 14:09 ` Maxime Devos
2021-09-02 14:20 ` Liliana Marie Prikler
2021-09-02 14:34 ` Maxime Devos
2021-09-01 19:48 ` Jonathan McHugh
2021-09-01 21:47 ` Liliana Marie Prikler
2021-09-02 13:32 ` Maxime Devos
2021-09-02 7:53 ` Jonathan McHugh
2021-09-02 9:25 ` Liliana Marie Prikler
2021-09-01 10:55 ` Xinglu Chen
2021-09-01 15:37 ` Leo Famulari
2021-09-01 16:50 ` Xinglu Chen
2021-09-02 16:51 ` Leo Famulari
2021-09-02 17:29 ` Leo Famulari
2021-09-03 16:11 ` Xinglu Chen
2021-09-03 16:35 ` Leo Famulari
2021-09-03 16:57 ` Leo Famulari
2021-09-03 20:03 ` Xinglu Chen
2021-09-04 21:00 ` Leo Famulari
2021-09-08 21:15 ` Ludovic Courtès
2021-09-02 17:08 ` Leo Famulari
2021-09-08 21:28 ` Ludovic Courtès
2021-09-08 22:21 ` Jonathan McHugh
2021-09-08 22:38 ` Leo Famulari
-- strict thread matches above, loose matches on Subject: below --
2021-09-03 5:51 Sarah Morgensen
2021-09-03 21:14 Sarah Morgensen
2021-09-03 22:11 ` Liliana Marie Prikler
2021-09-04 12:32 ` Taylan Kammer
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=8635qp1j6k.fsf@mgsn.dev \
--to=iskarian@mgsn.dev \
--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).