GNU bug report logs - #48028
[PATCH wip-gnome 0/8]: Misc.

Previous Next

Full log

View this message in rfc822 format

From: Leo Prikler <leo.prikler <at> student.tugraz.at>
To: Mark H Weaver <mhw <at> netris.org>, Raghav Gururajan <rg <at> raghavgururajan.name>,  48028 <at> debbugs.gnu.org
Subject: [bug#48028] [PATCH wip-gnome v4 3/8] gnu: gtkmm: Add missing native-input and correct propagated-inputs
Date: Fri, 07 May 2021 21:05:39 +0200

Am Freitag, den 07.05.2021, 14:40 -0400 schrieb Mark H Weaver:
> Hi Raghav,
> 
> Raghav Gururajan <rg <at> raghavgururajan.name> writes:
> 
> > I just realized packages that depend on gtkmm, doesn't propagate
> > it. So 
> > only way gtkmm, ends up in user-profiles is when explicitly
> > installed. 
> > Thus conflicts doesn't happen while building profiles right?
> 
> You might be right for users who only install user applications.
> 
> However, if I understand correctly, with the v4 patches that I looked
> at
> earlier, and presumably also the v5 patches (based on what you
> wrote), I
> guess that conflicts _would_ happen if someone tries to install
> 'gtkmm'
> and 'cairomm' together in the same profile.  It would be good to make
> that work properly, by selecting appropriate versions of these *mm
> packages that are compatible with each other.
> 
> What do you think?
> 
>       Regards,
>         Mark
As an addendum to what Mark said, I think this could be achieved by
temporarily hiding the variants of atkmm, cairomm, etc. that are
supposed to go with the yet unpackaged gtkmm and perhaps doing a round
of variable renames, so that those using manifests won't be screwed
either.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.