unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <leo.prikler@student.tugraz.at>
To: Maxime Devos <maximedevos@telenet.be>,
	Sarah Morgensen <iskarian@mgsn.dev>,
	 guix-devel@gnu.org
Subject: Re: Can we find a better idiom for unversioned packages?
Date: Thu, 02 Sep 2021 16:20:48 +0200	[thread overview]
Message-ID: <3b4f86e8ca7410b939f5a8da689919d1ab42f216.camel@student.tugraz.at> (raw)
In-Reply-To: <4042fc2a6124d218ffefbaa9c42dfa0e388dd1cd.camel@telenet.be>

Am Donnerstag, den 02.09.2021, 16:09 +0200 schrieb Maxime Devos:
> > > > > > 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.
> > > > Other versioning idioms would also be workarounds, wouldn't
> > > > they?
> > > > 
> > > > > > 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.
> > > > What purpose would extracting those serve however? 
> > > 
> > > Not losing the revision is useful for things like 
> > > <https://issues.guix.gnu.org/50072>;;, to be able to determine
> > > the old
> > > revision.  (That's not about inheriting packages though.)
> > Isn't that addressed by addressing the second point, though?  Like,
> > if
> > you know the source location of the revision, you can read it back
> > to
> > get the value itself (or possibly even access it as-is), no?
> 
> Indeed!  The patch [0] addresses the second point.  With that patch,
> the proposed <extension-version> isn't required.  But also: some
> people (at least Sarah?) consider [0] a work-around, and if guix used
> something like <extended-version>, [0] wouldn't be necessary.
> 
> It doesn't really matter to me what we'll end up using in guix
> in the long term, though in the short term, I would like something
> like [0] to be merged, as it is used by the (not-yet submitted, needs
> some cleanup, testing & rebasing) minetest updater, and it makes
> <https://issues.guix.gnu.org/50072> work in more cases.
That's not quite my point.  Sarah said that "inheriting definitions"
loses those values, which is true regardless of the merge of [0].  What
you said to answer my question w.r.t. why that matters was to repeat
the second point, which is addressed by [0].  In other words, what I'm
asking is why specifically inheriting (as in record inheriting) is made
to be such a big deal that it deserves its own point when I would
personally argue that it is not at all that important.

Greetings



  reply	other threads:[~2021-09-02 14:22 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 19:57 Can we find a better idiom for unversioned packages? Sarah Morgensen
2021-08-31 21:20 ` 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 [this message]
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=3b4f86e8ca7410b939f5a8da689919d1ab42f216.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=guix-devel@gnu.org \
    --cc=iskarian@mgsn.dev \
    --cc=maximedevos@telenet.be \
    /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).