[KDE/Mac] A (non)success story of digiKam on OSX/MacPorts involving kde4-workspace and qtcurve
René J.V. Bertin
rjvbertin at gmail.com
Sat Mar 14 15:15:45 UTC 2015
On Saturday March 14 2015 15:11:36 Marko Käning wrote:
> But at least this got me into testing digiKam after all and I figured out, that
> our 75yr-old former MacPorts user _might_ still be with us, if digiKam had had
> the ports
> kde4-workspace and qtcurve
> Actually kde4-workspace and qtcurve should be one of the first ports installed
> after kdelibs4. The question is now, how this could be organised:
> 2) Does it make sense to introduce a _metaport_, which depends on kdelibs4,
> qtcurve and kde4-workspace and which all other KDE ports should in turn
> depend on - instead of directly depending on kdelibs4?
That would be the best option IMHO, and one might even argue that kde4-workspace could be such a meta-port. Add kde4-baseapps, kde4-runtime and QtCurve as a replacement for the buggy Oxygen theme and you're close to what one might indeed call a KDE4 workspace on OS X.
Making all packages depend on this package might be a bit overkill, as this will be introducing dependencies on things like kdepimlibs and through that akonadi.
More information about the kde-mac