| Summary: | app-emulation/vmware-modules-2* should not DEPEND on app-emulation/vmware-{player,workstation} | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Markus Wernig <public> |
| Component: | New packages | Assignee: | Vadim Kuznetsov (RETIRED) <vadimk> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | jer, vmware+disabled |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Markus Wernig
2011-05-09 08:46:48 UTC
Another strange aspect is that it is not a runtime dependency but only a build time dependency. You would think it's either the former, or neither. (In reply to comment #0) > vmware-modules-238.4 for some reason depends on . modules are the part of vmware-player/workstation. That is the reason. > This breaks installations where vmware-modules is required without a graphical > runtime tool (or one not from Vmware). What does require vmware-modules beside vmware player/workstation/server? > > Besides, I fail to see the logic behind this dependency. Why would > vmware-modules require a player? > It can be used with any other virtualization > software (virtualbox etc. virtualbox has its own modules. > > I think this dependency should be dropped. > > Reproducible: Always > > Actual Results: > Cannot emerge vmware-modules-238.4 without vmware-player/workstation, which I > do not use (in fact, installing them breaks my configuration for > vmware-modules) > > Expected Results: > Be able do install vmware-modules standalone. (In reply to comment #1) > Another strange aspect is that it is not a runtime dependency but only a build > time dependency. You would think it's either the former, or neither. To be exact it's PDEPEND. (In reply to comment #2) > (In reply to comment #0) > > vmware-modules-238.4 for some reason depends on . > modules are the part of vmware-player/workstation. That is the reason. Yes, but it should be possible to install them standalone. The vmnet modules for example can be used in other contexts than just vmware player/workstation/server > > virtualbox has its own modules. Yes, but their functionality is quite different from that of vmware-modules. Combining both allows for far more advanced virtualization setups. Please reconsider this "bug". (OK, it's probably more of a feature request than a bug.) My problem is that it depends on both (version 238.5):
DEPEND="${RDEPEND}
|| ( =app-emulation/vmware-player-3.1.${PV_MINOR}*
=app-emulation/vmware-workstation-7.1.${PV_MINOR}* )"
but workstation has: !app-emulation/vmware-player"
and player has: !app-emulation/vmware-workstation"
So paludis can't install either, since it should be player || workstation, unless I'm misunderstanding the notation and it's a bug in paludis.
(In reply to comment #5) > My problem is that it depends on both (version 238.5): > DEPEND="${RDEPEND} > || ( =app-emulation/vmware-player-3.1.${PV_MINOR}* > =app-emulation/vmware-workstation-7.1.${PV_MINOR}* )" > > but workstation has: !app-emulation/vmware-player" > and player has: !app-emulation/vmware-workstation" > > So paludis can't install either, since it should be player || workstation, > unless I'm misunderstanding the notation and it's a bug in paludis. The idea is that you install player ( or workstation) and it will pull modules An you can't install modules without player or workstation, because it where modules comes from. |
