From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org, Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: Channel dependencies
Date: Wed, 24 Oct 2018 15:14:11 +0200 [thread overview]
Message-ID: <87tvlb32sc.fsf@gnu.org> (raw)
In-Reply-To: <87va5t2jl0.fsf@gmail.com> (Chris Marusich's message of "Tue, 23 Oct 2018 00:44:27 -0700")
Hello!
Chris Marusich <cmmarusich@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Good point. I agree that it’s similar to the question of propagated
>> inputs, which we deal with by reporting an error when a collision
>> arises.
>>
>> So, similarly, I think the safe way would be to report an error when
>> channel requirements conflict.
>
> With profiles, two packages conflict if and only if a file exists at the
> same relative path in both packages' outputs.
What you describe here are “soft collisions”, which the profile builder
reports as warnings (which are invisible with today’s ‘guix package’.)
I was referring to profile collisions where two packages with the same
name end up in the same profile (the ‘&profile-collision-error’
exception.)
This exception would also be raised if ‘guix pull’ ended up adding the
same channels more than once in ~/.config/guix/current.
> Also like you said, we can try to implement some heuristics to reject
> situations in which a "channel conflict" is likely. Would it be hard to
> change the channel mechanism so that it fails if there are any (normal)
> conflicts while generating the profile that contains all the channels?
> If we could prevent those (normal) conflicts while generating the
> profile, it would prevent a certain class of channel conflicts: namely,
> it would be impossible for two channels to provide the same guile
> modules.
‘union-build’ has a #:resolve-collision parameter. We could set it when
building ~/.config/guix/current so that an error is raised when the same
file is provided more than once.
(It’s a simple change we can make independently of what Ricardo is
proposing.)
WDYT?
>> We must define what it means for two <channel>s to conflict:
>>
>> • if a channel’s ‘commit’ is #f, then any channel with the same name
>> but a different ‘uri’ and/or a different ‘branch’ and/or a non-#f
>> commit conflicts;
>>
>> • if a channel’s ‘commit’ is not #f, then any channel with the same
>> name and otherwise different fields conflicts.
>
> This seems like a reasonable heuristic. What will we do when two
> channels differ only in their name? What about when two channels only
> have identical fields? Maybe in those cases we should just pick one,
> ignore the other, and log a warning, since their content will be the
> same.
Yes, they would effectively be ‘equal?’.
>> If we have inspiration later, we can liberalize this, for instance by
>> using several inferiors. It would be quite a bit of extra work, and
>> it’s not immediately clear to me how that could work. I believe what
>> Ricardo proposes already covers many use cases anyway.
>
> You're probably right. I'm just trying to think about how we might
> apply the functional model to this problem, rather than implementing
> heuristics. But maybe heuristics are good enough!
Sure, and that’s good!
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-10-24 13:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 6:54 Channel dependencies Ricardo Wurmus
2018-10-13 11:09 ` Pierre Neidhardt
2018-10-14 2:16 ` Chris Marusich
2018-10-14 9:49 ` Ricardo Wurmus
2018-10-15 9:29 ` Ludovic Courtès
2018-10-15 9:35 ` Ricardo Wurmus
2018-10-15 11:49 ` Ludovic Courtès
2018-10-15 9:41 ` Ludovic Courtès
2018-10-18 20:24 ` Ricardo Wurmus
2018-10-20 20:52 ` Chris Marusich
2018-10-22 12:04 ` Ludovic Courtès
2018-10-23 7:44 ` Chris Marusich
2018-10-24 13:14 ` Ludovic Courtès [this message]
2018-10-22 12:14 ` 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=87tvlb32sc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).