Why not use the googleearth-package package, which will let you make a proper .deb file that you can install with dpkg? First install googleearth-package (and also lsb-core if you don't have it already). Then, as user in your /home directory

Code:

make-googleearth-package

This will build the .deb file from your downloaded .bin file. If you are missing some dependencies, it will tell you, so you must install them. When the googleearth_6.0.0.xxxxxx.deb file is built, then (as root) you can copy it to /tmp and install it with dpkg.

Also, if you use the proprietary Nvidia driver (64-bit) and googleearth only shows you a black screen where the earth should be, then you need to install the nvidia-glx-ia32 package.

snvv

Post subject:Posted: 06.12.2010, 13:54

Joined: 2010-09-13
Posts: 329

Status: Offline

After all those new packages (*) installed as dependencies for the latest version of googleearth I decided to purge googleearth for my system.

Googleearth got bloated more and more, pulls in too many unrelated packages, does not build cleanly, is still closed source ... enough reasons to give it up. Marble is nice, and one can always use maps.google.com online, too.
Greetings,
Chris

Actually Marble itself doesn't necessarily depend on KDE. You can very easily build and package your own KDE-free version of Marble. For earlier Debian releases there was a package maintained that had no KDE dependencies. If you want to build the Qt only version just follow the instructions here:

Complaining about the "overhead" of the KDE libraries is a bit strange though if you compare it to Google Earth which comes with its own local copies of libraries like Qt, libicu and what not which potentially duplicate those installed on your system already ...