unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Jakub Kądziołka" <kuba@kadziolka.net>
Cc: 41882@debbugs.gnu.org
Subject: [bug#41882] [PATCH] channels: Allow specifying per-channel --allow-downgrades in the channel file
Date: Thu, 18 Jun 2020 13:59:11 +0200	[thread overview]
Message-ID: <874kr8mvow.fsf@gnu.org> (raw)
In-Reply-To: <20200617185027.ze5euqyuoylpewze@gravity> ("Jakub \=\?utf-8\?B\?S8SFZHppb8WCa2EiJ3M\=\?\= message of "Wed, 17 Jun 2020 20:50:27 +0200")

Hi,

Jakub Kądziołka <kuba@kadziolka.net> skribis:

>> > 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 ;)

I don’t think we can meaningfully support channels that are rebased all
the time.  I agree it’s a use case for some developers, and we need to
accommodate for that, but I wouldn’t want a general mechanism to mark a
channel as non-monotonic.

> Also, AFAIU, the channels.scm *is* the configuration file for guix
> pull, and it is the primary, if not only use of <channel>.

The <channel> data structure is used by ‘guix pull’, ‘guix
time-machine’, and ‘guix describe’.  It’s the primary way to communicate
information about the set of channels being used.  So to me it’s very
much orthogonal to whether one wants to allow downgrades, allow
offloading, and enable colored output.  :-)

WDYT?

Thanks,
Ludo’.




  reply	other threads:[~2020-06-18 12:00 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
2020-06-18 11:59     ` Ludovic Courtès [this message]
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=874kr8mvow.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=41882@debbugs.gnu.org \
    --cc=kuba@kadziolka.net \
    /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).