unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 27467@debbugs.gnu.org
Subject: bug#27467: Xfce broken, because it propagates two different versions of gtk+
Date: Tue, 27 Jun 2017 15:45:49 +0200	[thread overview]
Message-ID: <874lv15ysy.fsf@gnu.org> (raw)
In-Reply-To: <87r2y5euec.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 27 Jun 2017 09:56:11 +0200")

Hi!

Ricardo Wurmus <rekado@elephly.net> skribis:

> What do you think of the attached patches?  The first makes libxfce4ui
> only propagate the latest gtk+, so I added gtk+-2 where needed.  The
> second removes “exo” from the “xfce” meta-package, because it doesn’t
> seem needed.  “exo” propagates “gtk+-2”, so it would be hard to prevent
> the conflict otherwise.
>
> These patches are only a temporary fix until we can find a way to mark
> certain conflicts as unproblematic.

These patches seem reasonable to me.

Another option (perhaps slightly less intrusive) would be to implement
the ‘xfce’ meta-package using ‘union-build’ instead of
‘propagated-inputs’.

Thanks,
Ludo’.

  reply	other threads:[~2017-06-27 13:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 23:47 bug#27467: Xfce broken, because it propagates two different versions of gtk+ Mark H Weaver
2017-06-24  9:41 ` ng0
2017-06-24 21:53 ` Ludovic Courtès
2017-06-25  9:16   ` Mark H Weaver
2017-06-26 11:14     ` Ricardo Wurmus
2017-06-26 16:14       ` Ludovic Courtès
2017-06-26 17:03         ` ng0
2017-06-27  5:25         ` Ricardo Wurmus
2017-06-27  7:56           ` Ricardo Wurmus
2017-06-27 13:45             ` Ludovic Courtès [this message]
2017-06-29 14:12               ` Ricardo Wurmus
2017-06-29 16:01                 ` Mark H Weaver

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=874lv15ysy.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27467@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).