Marble 0.5.1 is out ...it is the same as in KDE 4.0.1, but as it does not depend on KDE itself, I think it might be nice if it either: * got at the same time also a separate ebuild in sci-geosciences, or * when the kde-base/marble ebuild gets rid of KDE dependancies, that users of sci-geosciences/marble would get informed by portage to emerge kde-base/marble
(In reply to comment #0) > Marble 0.5.1 is out ...it is the same as in KDE 4.0.1, but as it does not > depend on KDE itself, I think it might be nice if it either: > * got at the same time also a separate ebuild in sci-geosciences, or > * when the kde-base/marble ebuild gets rid of KDE dependancies, that users of > sci-geosciences/marble would get informed by portage to emerge kde-base/marble As maintaining the exact same ebuild twice is rather pointless, I've added a "kde" USE flag, to make KDE dependencies optional. CC'ing cryos as he maintains sci-geosciences/marble.
I totally agree although I am not certain how this affects keywording etc? Marble without the Qt deps could arguably go stable some time soon whereas the KDE version should be hard masked. Is there a reasonable way to deal with this? I have not looked at this in a while but would like to see marble widely used and am hoping that KDE 4 will be unmasked within the near future and so alleviate this. Otherwise I can see an argument for having two ebuilds to satisfy the keywording issues. I am open to suggestions though. There are one or two other apps that may have similar issues - adding the kde USE flag could introduce a dependency on a hard masked kdelibs...
