[ebuild N ] net-misc/networkmanager-0.6.6 USE="crypt gnome -debug -doc" [ebuild N ] gnome-base/gnome-panel-2.22.2 USE="eds networkmanager -debug -doc" * Error: circular dependencies: ('ebuild', '/', 'gnome-base/gnome-panel-2.22.2', 'merge') depends on ('ebuild', '/', 'net-misc/networkmanager-0.6.6', 'merge') (hard) ('ebuild', '/', 'net-misc/networkmanager-0.6.6', 'merge') depends on ('ebuild', '/', 'gnome-base/gnome-panel-2.22.2', 'merge') (hard)
I was about to fill in different but related bug. I think that both net-misc/networkmanager and gnome-extra/nm-applet do not need to depend on gnome-panel at all. They both builds without gnome-panel and work fine with xfce4-panel.
Steev, Gilles and I discussed this a couple days ago and Steev agreed that a || (gnome-panel xfce-panel) dep was ok. We could even put it in PDEPEND, as it's only a dep to have a notification area of some sort. Steev, feel free to correct anything I said :) Cheers
(In reply to comment #2) > Steev, Gilles and I discussed this a couple days ago and Steev agreed that a || > (gnome-panel xfce-panel) dep was ok. Hm, but then what about other panels? [U] gnome-base/gnome-panel (2.24.1-r1@10.12.2008 -> (~)2.24.2-r1): The GNOME panel [N] lxde-base/lxpanel (~0.3.8.1!t): Lightweight X11 desktop panel for LXDE [N] x11-misc/fbpanel (4.12): light-weight X11 desktop panel [N] x11-misc/fspanel (0.8_beta1-r2!s): F***ing Small Panel. Good (and small) replacement for gnome-panel [N] x11-misc/pypanel (2.4): PyPanel is a lightweight panel/taskbar for X11 window managers. [N] x11-misc/suxpanel (0.4b-r1): SuxPanel is a complete rewrite of MacOS Style Panel, a light-weight X11 desktop panel [N] x11-misc/bmpanel [1] (--): BMPanel (BitMap Panel) is a lightweight, NETWM compliant panel for X11 Window System. [N] x11-wm/matchbox-panel (~0.9.3): The Matchbox Panel [N] xfce-base/xfce4-panel (4.4.3): Panel I haven't checked them, but some of them could work with nm-applet either... > We could even put it in PDEPEND, as it's only a dep to have a notification > area of some sort. It's hard to imagine desktop without notification area. So I don't think we need this dependency at all... If user is not so experienced with desktops she'll emerge complete desktop solution, like gnome/kde/xfce4 and will have panel with notification area started (via start{kde,xfce4,gnome}). If user want something unusual, tweaks something, having panel in and *DEPEND does merge panel (which probably user don't want) but this merge doesn't help user to have desktop with notification area - she has to start panel manually and put notification area there... So for first category of users this dependency does nothing for second it complicates things. Is there any reason not to drop this dependency completely?
Steev told us that he put the dep there in the first place because users didn't understand how nm-applet operated... Steev, as you're the maintainer, I'll let you explain what your reasons are :) Cheers
(In reply to comment #2) > Steev, Gilles and I discussed this a couple days ago and Steev agreed that a || > (gnome-panel xfce-panel) dep was ok. Ok, currently I've commited this. But I'm really looking forward to remove this panel dependency entirely.
This bug is about the circular dependency, not discussion of notification areas. For the circular dep, we can probably hack gnome-panel to import networkmanager headers or something along those lines, as it probably only needs the header for D-Bus API description and doesn't actually link against NM. Just a guess though. Perhaps having a separate package for NM headers could be another option. There are many packages whose only real need for NM is because of the header. They could just have it hard-_build_-depend on that header always and be done with it. For most cases it would just build the support and continue working happily if no-one has installed NetworkManager (yet). But this all is something to think about in the global context - gnome-panel, epiphany, and more.
Mart, this hacks are not necessary and are overkill since nothing in networkmanager requires gnome-panel. I even don't see why networkmanager needs panel. As I see better solution will be move panel dependency out but can somebody else confirm that this is god/bad solution?
And I don't think anything in gnome-panel depends on NetworkManager. It just wants to know when you go offline for disabling clock-applet weather information retrieval handling for that time, and that should be just pure D-Bus, no runtime depending on NM should be necessary and the build-time dep could be lighter.
can you please finally remove all *-panel dependencies from networkmanager!?
I'm having this problem on a newly built system only with the gnome-base/gnome-panel-2.24.3-r1 package instead of gnome-base/gnome-panel-2.22.2 Are there still plans to remove the panel dependencies?? Will compile without networkmanager USE flag for now, to get GNOME up and running.
Can we please remove the panel deps in nm? It doesn't need the panel at all. nm-applet, maybe, but not nm.
*networkmanager-0.7.1 (22 Apr 2009) 22 Apr 2009; Robert Buchholz <rbu@gentoo.org> -networkmanager-0.6.5_p20070823.ebuild, networkmanager-0.6.6.ebuild, +networkmanager-0.7.1.ebuild: Version bump by Robert Piasek. Fixes bug 266184. Remove 0.6.5 version, remove dependency on gnome/xfce panels as they are pulled in via nm-applet anyway (bug 246023).
(In reply to comment #12) > *networkmanager-0.7.1 (22 Apr 2009) > > 22 Apr 2009; Robert Buchholz <rbu@gentoo.org> > -networkmanager-0.6.5_p20070823.ebuild, networkmanager-0.6.6.ebuild, > +networkmanager-0.7.1.ebuild: > Version bump by Robert Piasek. Fixes bug 266184. > Remove 0.6.5 version, remove dependency on gnome/xfce panels as they > are pulled in via nm-applet anyway (bug 246023). and what about kde users?
(In reply to comment #13) > (In reply to comment #12) > > *networkmanager-0.7.1 (22 Apr 2009) > > > > 22 Apr 2009; Robert Buchholz <rbu@gentoo.org> > > -networkmanager-0.6.5_p20070823.ebuild, networkmanager-0.6.6.ebuild, > > +networkmanager-0.7.1.ebuild: > > Version bump by Robert Piasek. Fixes bug 266184. > > Remove 0.6.5 version, remove dependency on gnome/xfce panels as they > > are pulled in via nm-applet anyway (bug 246023). > > and what about kde users? If you use KDE, why would you need the gnome panel?
(In reply to comment #14) > If you use KDE, why would you need the gnome panel? There is no need for the gnome panel in KDE, but KDE users actually do use gnome-extra/nm-applet which depends on || ( >=gnome-base/gnome-panel-2 xfce-base/xfce4-panel x11-misc/trayer ) so kde users should depend on gnome-panel, xfc4-panel or trayer if they want to use nm-applet?! imho the panel dependency should be removed. if one wants to use a graphical network configuration tool there (most probably) already is a desktop environment/window manager installed.
(In reply to comment #15) > There is no need for the gnome panel in KDE, but KDE users actually do use > gnome-extra/nm-applet which depends on > || ( >=gnome-base/gnome-panel-2 xfce-base/xfce4-panel x11-misc/trayer ) > so kde users should depend on gnome-panel, xfc4-panel or trayer if they want to > use nm-applet?! > Maybe there should be a new virtual for "panel" :p
(In reply to comment #16) > Maybe there should be a new virtual for "panel" :p I was thinking the same thing, but this is something for the desktop project to decide.
Maybe a bit late to this argument: But please could we remove the panel dependencies from nm-applet? They just make no sense from my view. For instance I am currently using NetworkManager from GNOME Shell, no need for any of the listed panels. I could also use GNOME-Do and lots of other tools which implement the systray specification. Do we really want to keep an endless list of all of these panels, starters, whatever? Also having a dep on certain panels / docks / launchers doesn't tell you if people are actually running it with a notification area enabled, so there really is no reliable gain for the users. The panel information would be really better suited for a helpful postinst-message or some desktop documentation....
*** Bug 344961 has been marked as a duplicate of this bug. ***
All versions of networkmanager and nm-applet currently in portage do not depend on gnome-panel.
