all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: Warning on using GUIX_PACKAGE_PATH
Date: Thu, 9 Feb 2017 15:08:35 +0100	[thread overview]
Message-ID: <20170209140835.GA30957@jocasta.intra> (raw)
In-Reply-To: <20170209133048.GA23419@mail.thebird.nl>

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

On Thu, Feb 09, 2017 at 01:30:48PM +0000, Pjotr Prins wrote:
     @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.


Those are indeed cavaets.  But whether they are "downsides" or "largish" is
a matter for individual users to decide.

Some people 1) don't want to share the pacakges they create; and/or 2) are
prepared to accept the effort keeping the two things in sync.

J'

     

-- 
Avoid eavesdropping.  Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2017-02-09 14:08 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 [this message]
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

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=20170209140835.GA30957@jocasta.intra \
    --to=john@darrington.wattle.id.au \
    --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.