From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 41882@debbugs.gnu.org
Subject: [bug#41882] [PATCH] channels: Allow specifying per-channel --allow-downgrades in the channel file
Date: Wed, 17 Jun 2020 20:50:27 +0200 [thread overview]
Message-ID: <20200617185027.ze5euqyuoylpewze@gravity> (raw)
In-Reply-To: <87lfkmrqi7.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
> > It gets tiring to have to specify --allow-downgrades when pulling, so I
> > added a way of specifying it in the channels file. As a bonus, it's more
> > granular.
> >
> > If this is the right approach, I'll add some docs. Also, is there a test
> > that exercises this function?
>
> I don’t think “allow-downgrade?” should be a property of <channel>,
> because conceptually it’s an unrelated piece of configuration. So I
> think it’s configuration that belongs elsewhere, but there’s no
> configuration file for ‘guix pull’ etc.
It's a property of the channel that the git repo in question is not
monotonic ;) Also, AFAIU, the channels.scm *is* the configuration file
for guix pull, and it is the primary, if not only use of <channel>.
Regards,
Jakub Kądziołka
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-17 18:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 21:03 [bug#41882] [PATCH] channels: Allow specifying per-channel --allow-downgrades in the channel file Jakub Kądziołka
2020-06-17 9:27 ` Ludovic Courtès
2020-06-17 18:50 ` Jakub Kądziołka [this message]
2020-06-18 11:59 ` Ludovic Courtès
2020-06-18 23:52 ` Jakub Kądziołka
2020-06-19 0:19 ` [bug#41882] Guix configuration file? zimoun
2020-06-19 7:39 ` Ludovic Courtès
2020-06-19 7:52 ` [bug#41882] [PATCH] channels: Allow specifying per-channel --allow-downgrades in the channel file Ludovic Courtès
2020-06-19 12:25 ` Jakub Kądziołka
2020-06-19 20:26 ` 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=20200617185027.ze5euqyuoylpewze@gravity \
--to=kuba@kadziolka.net \
--cc=41882@debbugs.gnu.org \
--cc=ludo@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).