From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 27467-done@debbugs.gnu.org
Subject: bug#27467: Xfce broken, because it propagates two different versions of gtk+
Date: Thu, 29 Jun 2017 16:12:17 +0200 [thread overview]
Message-ID: <87podm9932.fsf@elephly.net> (raw)
In-Reply-To: <874lv15ysy.fsf@gnu.org>
Hi,
Ludovic Courtès <ludo@gnu.org> writes:
> 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’.
Yes, that’s better. I pushed two commits:
gnu: libxfce4ui: Do not propagate gtk+-2.
(b8d3a000efca885180277358caa3c4fe604168a5)
gnu: xfce: Build union instead of propagating inputs.
(c860d6ef235b47ec8181fbf390e0b42fbc95dcfe)
With these two commits I can install xfce without problems.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-06-29 14:13 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
2017-06-29 14:12 ` Ricardo Wurmus [this message]
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=87podm9932.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=27467-done@debbugs.gnu.org \
--cc=ludo@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 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).