unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Tim Lee <progscriptclone@gmail.com>
Cc: phil@beadling.co.uk, help-guix@gnu.org
Subject: Re: GUIX_PACKAGE_PATH doesn't have priority over official guix packages
Date: Sun, 17 Oct 2021 13:36:17 +0200	[thread overview]
Message-ID: <87h7dfc1pt.fsf@nckx> (raw)
In-Reply-To: <20211016222911.ex2z4acagxyrgipb@localhost>

[-- Attachment #1: Type: text/plain, Size: 873 bytes --]

Tim Lee 写道:
>> 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.

TBH I don't really understand what that second sentence is trying 
to say, so I can't judge whether it's misleading or not.

How about something like

  “Any packages they define will be added to the pool of available 
  packages.  Standard package specification rules apply: when 
  given a package name without an unambiguous version number, Guix 
  will always pick the highest version of that package regardless 
  of where it came from.”

?

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

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

  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=87h7dfc1pt.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=phil@beadling.co.uk \
    --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.
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).