all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Phil <phil@beadling.co.uk>
To: Tim Lee <progscriptclone@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: GUIX_PACKAGE_PATH doesn't have priority over official guix packages
Date: Sun, 17 Oct 2021 09:10:54 +0100	[thread overview]
Message-ID: <87wnmcax69.fsf@beadling.co.uk> (raw)
In-Reply-To: <20211016222911.ex2z4acagxyrgipb@localhost>


Tim Lee writes:

>> Environment Variable: GUIX_PACKAGE_PATH
>>
>> This is a colon-separated list of directories to search for additional
>> package modules. Directories listed in this variable take precedence
>> over the own modules of the distribution.
>
> The last sentence makes it sound like GUIX_PACKAGE_PATH will always have
> precedence over the official guix channel.

I think the doc should specify "all else being equal" - my own trail and
error testing seem to suggest that when versions are equal, Guix will then prefer the
package specified by "-L" or "GUIX_PACKAGE_PATH" - however a higher version seems to always win, wherever it is specified.

2 Caveats -

This is just by observation only, perhaps someone else can
comment if this is intended or not.

I used time-machine to test this but I don't think that
should change things.  I was able to move backwards and forwards in time
vs a local package I have specified.  My local package was taken when I
moved backwards in time, but when I moved forwards to a newer version in
Guix it took the remote package instead.  When the package was the same
as remote it took the version with a local location - as far as I can
tell.



  reply	other threads:[~2021-10-17  8:11 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 [this message]
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

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=87wnmcax69.fsf@beadling.co.uk \
    --to=phil@beadling.co.uk \
    --cc=help-guix@gnu.org \
    --cc=progscriptclone@gmail.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.