all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: guix-devel@gnu.org
Subject: Xfce collision
Date: Thu, 25 Feb 2016 21:36:58 +0100	[thread overview]
Message-ID: <20160225203658.GA24846@solar> (raw)

Hello,

when installing xfce, there is a collision with xfce4-session for the file
startxfce4.

The reason is the following:
       (alist-replace
        'install
        (lambda* (#:key outputs #:allow-other-keys)
          (let* ((out  (assoc-ref outputs "out"))
                 (bin  (string-append out "/bin"))
                 (prog (string-append bin "/startxfce4")))
            (mkdir-p bin)
            (symlink (string-append
                      (assoc-ref %build-inputs "xfce4-session")
                      "/bin/startxfce4")
                     prog)
            (wrap-program prog
              ;; For xfce4-panel plugins.
              `("X_XFCE4_LIB_DIRS" = ,(list (getenv "X_XFCE4_LIB_DIRS"))))))
    (propagated-inputs
     ...
       ("xfce4-session"        ,xfce4-session)

So if I understand correctly, the startxfce4 of xfce will end up being a
wrapped version of the one in xfce4-session. However, if both are installed,
could it not be possible that the non-wrapped version ends up in the profile?

Andreas

             reply	other threads:[~2016-02-25 20:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 20:36 Andreas Enge [this message]
2016-02-29  8:46 ` [PATCH] gnu: xfce: Don’t wrap startxfce4. (Re: Xfce collision) 宋文武
2016-03-01 21:26   ` Ludovic Courtès
2016-03-02  0:33     ` [PATCH] gnu: xfce: Don’t wrap startxfce4 宋文武
2016-02-29  8:47 ` [PATCH] gnu: xfce: Don’t wrap startxfce4. (Re: Xfce collision) 宋文武
2016-02-29  8:48 ` 宋文武
2016-02-29  8:49 ` 宋文武
2016-02-29  8:50 ` 宋文武
2016-02-29  8:50 ` 宋文武
2016-02-29  9:26   ` 宋文武
2016-02-29  8:50 ` 宋文武
2016-02-29  8:50 ` 宋文武
2016-02-29  8:50 ` 宋文武

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=20160225203658.GA24846@solar \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.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.