From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel@gnu.org
Subject: Re: potluck in the house
Date: Wed, 19 Apr 2017 22:27:55 +0200 [thread overview]
Message-ID: <87r30om9bo.fsf@gnu.org> (raw)
In-Reply-To: <878tmy43dl.fsf@igalia.com> (Andy Wingo's message of "Tue, 18 Apr 2017 08:49:10 +0200")
Andy Wingo <wingo@igalia.com> skribis:
> On Fri 14 Apr 2017 14:54, ludo@gnu.org (Ludovic Courtès) writes:
>
>>> I think we should make it so that the lower-potluck-package process
>>> prefers "core" packages if available, and only goes to the channel if
>>> the core does not provide a package matching the specification.
>>>
>>> I think this is a question for the design of channels though: how to
>>> resolve dynamically scoped (specification->package) links in the
>>> presence of channels.
>>
>> ‘specification->package’ already transparently handles things in
>> GUIX_PACKAGE_PATH, so I suspect it wouldn’t be very different.
>>
>> WDYT?
>
> I don't know. I see a danger if person A makes a potluck package for
> that depends on Guile, and person B makes a potluck package for some
> development version of Guile with a later version number. Person A (and
> person A's users) probably don't expect to be using a development
> Guile, so the specifications in person A's package should probably *not*
> resolve person B's guile as the "best" one. See what I'm saying?
> Tricky stuff. A hierarchy of potential sources sounds best to me so
> that specification->package only looks for "guile" in the potluck
> GUIX_PACKAGE_PATH if it's not found (possibly with the version
> constraint) in the "main" GUIX_PACKAGE_PATH.
Indeed, good point. We should have a way to say that some channels have
precedence over other channels.
Ludo’.
prev parent reply other threads:[~2017-04-19 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 13:25 potluck in the house Andy Wingo
2017-04-13 15:42 ` Ludovic Courtès
2017-04-13 16:20 ` Andy Wingo
2017-04-14 12:54 ` Ludovic Courtès
2017-04-18 6:49 ` Andy Wingo
2017-04-19 20:27 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r30om9bo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=wingo@igalia.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.