google released the first Beta version of googleearth. I slightly modified the old ebuild. It seems not to need the mime-magic.path anymore. It does not install libcrypt.so, because it conflicts with libssl.so
Created attachment 180852 [details] googleearth-5.0.0_beta1.ebuild Hopefully a good ebuild, maybe modifications needed
Of course, it is not the first beta version of googleearth, but of googleearth 5.0.
Hello, you have keyworded it -amd64; it works for me on Turion64 X2 with nvidia-drivers. So I recommend to switch it to amd64.
My apologies for the clutter... ~amd64, to be precise.
Comment on attachment 180852 [details] googleearth-5.0.0_beta1.ebuild I switched to ~amd64 keyword. And deleted th String after $Header , which wasn't correct.
Created attachment 180884 [details] googleearth-5.0.0_beta1.ebuild
The ebuild should be renamed to googleearth-5.0.11337.1968_beta.ebuild, because this matches the exact Version, as it was done in previous releases of googleearth-ebuilds.
> The ebuild should be renamed to googleearth-5.0.11337.1968_beta.ebuild, > because this matches the exact Version, as it was done in previous releases > of googleearth-ebuilds. I believe it should rather be named googleearth-9999.ebuild. The ebuild's SRC_URI points to http://dl.google.com/earth/client/current/GoogleEarthLinux.bin. This path implies a -9999 version. If the ebuild were named googleearth-5.0.11337.1968_beta.ebuild, the SRC_URI should point to something like "yada://yada/yada/GoogleEarthLinux-${PV}.bin" or "yada://yada/release-${PV}/GoogleEarthLinux.bin". Google has a rather mysterious directory structure on their servers, so a 9999-version ebuild might actually prevent problems like Bug 256267.
(In reply to comment #9) > I believe it should rather be named googleearth-9999.ebuild. The ebuild's > SRC_URI points to > http://dl.google.com/earth/client/current/GoogleEarthLinux.bin. This path > implies a -9999 version. > Google has a rather mysterious directory structure on their servers, so a > 9999-version ebuild might actually prevent problems like Bug 256267. This sadly would not work either, as the Manifest file contains hashes of the distfile, so when google updates it, Manifest check fails. People would still have to fill bugs and the updated file would need to be redigested. By versioning the ebuild and bumping the version on the redigests, people who installed the older version will automatically get the update, with 9999 they would have to check themselves. Also with EAPI=2 SRC_URI arrows we at least can version the distfile in people's DISTDIR so they can go back to the older version they have already downloaded if the new version has problems, as the distfiles don't overwrite themselves. Anyway, bumped, thanks.
