The package x11-themes/fluxbox-styles-fluxmod-20050128-r1 depends on >=x11-wm/fluxbox-0.9.11. I think it's clear that instaling fluxbox styles without fluxbox does not make that much sense. But the fluxbox styles do definitely not need the fluxbox window manager for installation! I have previously (before installing the styles) installed fluxbox from portage, but then decided that I will switch to the portage overlay from the fluxbox developers. I unmerged x11/fluxbox and now when I'm running a deep update I get an unresolved dependency, because I have masked x11-wm/fluxbox (otherwise emerge would want to reinstall it for fluxmod). The output looks like this: emerge -Dua world These are the packages that would be merged, in order: Calculating world dependencies - !!! All ebuilds that could satisfy ">=x11-wm/fluxbox-0.9.11" have been masked. !!! One of the following masked packages is required to complete your request: - x11-wm/fluxbox-1.0.0-r2 (masked by: package.mask) - x11-wm/fluxbox-1.0.0 (masked by: package.mask) - x11-wm/fluxbox-0.9.15.1-r2 (masked by: package.mask) For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. (dependency required by "x11-themes/fluxbox-styles-fluxmod-20050128-r1" [installed]) !!! Problem resolving dependencies for x11-themes/fluxbox-styles-fluxmod !!! Depgraph creation failed. Because x11-wm/fluxbox is an unnecessary dependency you should remove it from the fluxbox-styles-fluxmod package. It causes unnecessary problems (as you can see). Reproducible: Always
*** Bug 229809 has been marked as a duplicate of this bug. ***
*** Bug 229813 has been marked as a duplicate of this bug. ***
*** Bug 229815 has been marked as a duplicate of this bug. ***
*** Bug 229817 has been marked as a duplicate of this bug. ***
*** Bug 229819 has been marked as a duplicate of this bug. ***
*** Bug 229823 has been marked as a duplicate of this bug. ***
*** Bug 229825 has been marked as a duplicate of this bug. ***
(In reply to comment #0) > Because x11-wm/fluxbox is an unnecessary dependency you should remove it from > the fluxbox-styles-fluxmod package. It causes unnecessary problems (as you can > see). No, the problem comes from you using an external ebuild. If you were using the Portage tree's ebuild, you wouldn't suffer these troubles. I don't know about any overlay from the fluxbox developpers. The closest thing that I know of is Akira's ebuild: http://darkshed.net/files/gentoo/ebuilds/x11-wm/ak-fluxbox-git/ Since his ebuild is called ak-fluxbox-git, Portage thinks you didn't installed fluxbox. I guess you could use /etc/portage/package.provided to solve this issue, but I think it's not the best solution, so I chose to update/fix Akira's ebuild. You can find my version here: http://dev.azatom.info/projects/dotfiles/browser/portage/x11-wm/fluxbox Or directly from my SVN repository: svn co http://dev.azatom.info/svn/dotfiles/browser/portage/x11-wm/fluxbox fluxbox It still lacks of a few USE flags though.
ak|ra (Mathias Gumz) is a fluxbox developer, although his ebuild is not endorsed by the project. At any rate, I'm going to agree with the original poster. While the styles may not be _useful_ without fluxbox (or blackbox), they don't _require_ fluxbox. A user may have fluxbox installed by other means, or he may just want the styles installed on a data server so they can be accessed by other computers on the network. I realize that a similar argument could be made for other software and that it would be absurd for those cases. I don't expect portage to know when a user has installed software manually (but it would be nice!). However, fluxbox is not a library or command line utility, and it doesn't currently support plugins. There's no good reason for anything to depend on it.
(In reply to comment #9) > or he may just want the styles installed on a data server so they can be > accessed by other computers on the network. Having the files available on a machine is different than having it installed on the system, so this precise example is invalid. > I don't expect portage to know when a user has > installed software manually (but it would be nice!). Portage is nice, and /etc/portage/package.provided is the way. > However, fluxbox is not a > library or command line utility, and it doesn't currently support plugins. > There's no good reason for anything to depend on it. I just wanted to make a difference between the problem Geralt had (and how he could have solved it), but that doesn't make the background point invalid ; this one is more about the (R)DEPENDS policy, so I'll pass on it.
fixed.
