all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: EuAndreh <eu@euandre.org>
Cc: 44810@debbugs.gnu.org
Subject: [bug#44810] [PATCH v3] gnu: Add git-open.
Date: Thu, 26 Nov 2020 14:00:15 -0500	[thread overview]
Message-ID: <X7/7P77e9vdqfOtD@jasmine.lan> (raw)
In-Reply-To: <871rggno4z.fsf@euandre.org>

On Thu, Nov 26, 2020 at 12:17:32PM -0300, EuAndreh wrote:
> Leo Famulari <leo@famulari.name> writes:
> 
> > It might cause trouble for users to propagate xdg-utils, but we'll cross
> > that bridge when we come to it. Guix isn't really that convenient for
> > shell scripts.
> 
> Why is that? If more than one package propagates xdg-utils, won't they
> all share the same xdg-utils?

Yes, if the entire profile was based on a Guix version that used the
same xdg-utils. But it's a design goal of Guix to allow profiles that
are a "mix" of versions.

> It would be a problem when to different builds of xdg-utils are
> propagated, and they become conflicting. Is that what you're referring
> to?

Yes. Sometimes this limitation is difficult to work around, especially
if the programming language of the packages in question doesn't easily
permit referring to dependencies — like the Unix shell language.




      reply	other threads:[~2020-11-26 19:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23  1:17 [bug#44810] [PATCH] gnu: Add git-open EuAndreh via Guix-patches via
2020-11-23 11:44 ` EuAndreh via Guix-patches via
2020-11-25 23:01   ` Leo Famulari
2020-11-23 19:44 ` [bug#44810] [PATCH v3] " EuAndreh via Guix-patches via
2020-11-25 23:06   ` Leo Famulari
2020-11-26 15:17     ` EuAndreh via Guix-patches via
2020-11-26 19:00       ` Leo Famulari [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=X7/7P77e9vdqfOtD@jasmine.lan \
    --to=leo@famulari.name \
    --cc=44810@debbugs.gnu.org \
    --cc=eu@euandre.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.
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.