From: Paul Jewell <paul@teulu.org>
To: help-guix@gnu.org
Subject: Re: GUIX_PACKAGE_PATH doesn't have priority over official guix packages
Date: Mon, 18 Oct 2021 14:48:20 +0100 [thread overview]
Message-ID: <5bab993d-506e-962d-bd87-18db6b4e0db5@teulu.org> (raw)
In-Reply-To: <CAOvsyQsAf6WLuiSucBoyRntu-2T_r78KtXuJezrzBK1TdkgUCw@mail.gmail.com>
Just a small thought:
On 16/10/2021 22:03, Phil Beadling wrote:
> As far as I can see, Guix will always prefer the highest version number
> irrspective of which channel is sources it from.
>> However, if there is a package with the same name in both my channel and
>> in the official guix channel, 'guix install' will install from the
>> official guix channel instead of my channel. Is this supposed to happen?
>> I thought that GUIX_PACKAGE_PATH is supposed to have priority over
>> the official guix channel?
>>
>> I am currently working around this problem by specifying the version
>> number when installing. For example:
>>
>> $ GUIX_PACKAGE_PATH=. guix install 'mypackage@1.2.3'
This is a similar situation you see in the gentoo world with an overlay
(similar to non core channel) containing an ebuild (package definition)
for a package which also exists in the main repo. The highest version
number will be selected by default, regardless of the ebuild location.
The solution there is to allow the overlay source to be included in the
package definition:
emerge -av my-package::my-overlay
[emerge is the command which installs packages]
It is also allowed to pin a particular version of the package, but if
the package exists in both the overlay and the main repo, I am not sure
what will happen.
Perhaps in the future a similar method could be used to pin a particular
channel for a package? It is quite useful to ensure the latest package
continues to be installed without having to change the version number in
the package list.
--
Paul
prev parent reply other threads:[~2021-10-18 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 8:45 GUIX_PACKAGE_PATH doesn't have priority over official guix packages Tim Lee
2021-10-16 21:03 ` Phil Beadling
2021-10-16 22:29 ` Tim Lee
2021-10-17 8:10 ` Phil
2021-10-17 11:36 ` Tobias Geerinckx-Rice
2021-10-17 12:15 ` Phil
2021-10-17 12:31 ` Tobias Geerinckx-Rice
2021-10-17 13:56 ` Tim Lee
2021-10-18 13:48 ` Paul Jewell [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
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=5bab993d-506e-962d-bd87-18db6b4e0db5@teulu.org \
--to=paul@teulu.org \
--cc=help-guix@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.
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).