From: ludo@gnu.org (Ludovic Courtès)
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: Warning on using GUIX_PACKAGE_PATH
Date: Fri, 10 Feb 2017 13:33:29 +0100 [thread overview]
Message-ID: <87inoifco6.fsf@gnu.org> (raw)
In-Reply-To: <20170209133048.GA23419@mail.thebird.nl> (Pjotr Prins's message of "Thu, 9 Feb 2017 13:30:48 +0000")
Hello,
Pjotr Prins <pjotr.public12@thebird.nl> skribis:
> @FOSDEM we concluded that GUIX_PACKAGE_PATH does not necessarily work
> that wel. I added to my guix-notes the following:
>
> +Note that, even though GUIX_PACKAGE_PATH can be a feasible way of
> +adding and maintaining packages, it has two largish downsides: (1) it
> +is removed from the main package tree and therefore not easily shared
> +and integrated and (2) to remain compatible you need to juggle two git
> +trees which may go out of synch.
I’m not sure who “we” is. :-)
Anyway I think GUIX_PACKAGE_PATH is just that: an environment variable
that allows users to add more packages to Guix’s search path. It has
never pretended to do more than this, so in that sense the downsides you
mention are “expected”.
It does mean that a higher-level mechanism like channels would be more
than helpful, but it doesn’t mean that GUIX_PACKAGE_PATH is “broken” per se.
Ludo’.
prev parent reply other threads:[~2017-02-10 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 13:30 Warning on using GUIX_PACKAGE_PATH Pjotr Prins
2017-02-09 14:08 ` John Darrington
2017-02-09 16:50 ` ng0
2017-02-09 21:14 ` Pjotr Prins
2017-02-09 19:41 ` Andreas Enge
2017-02-10 12:33 ` 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=87inoifco6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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.