severity 378362 wishlist
thanks

On Saturday 15 July 2006 10:50, Julien Valroff wrote:
> I ran a lintian test on the generated binary package and was quite
> surprised when I saw the results (see attached file).

Having the generated googleearth binary package be lintian clean like a real 
Debian package is not a high-priority goal of googleearth-package since the 
generated binary package is completely non-distributable, but I agree that 
it would be nice.

If you (or anyone else) are motivated, Patches to fix any of the following 
would be helpful 

> To sum up, you will need to:
>   * Write a short man page for googleearth

For this it would be easy to make a stub, but I don't think it takes any 
command-line options other than kml/kmz files. If you know any different, 
let me know. 

>   * Move images from /usr/lib/ to /usr/share/ (I don't know if it is
> possible), and change their permissions to 644

Not sure that's possible, the paths are all hardcoded, and googleearth even 
has to run with a certain working-directory set to even link properly 
because of rpath issues.

>   * Add a copyright file - the license is available online on
>     http://earth.google.com/support/bin/answer.py?answer=34344&topic=1151
> and is installed in each supported language in
> /usr/lib/googleearth/resources/*.locale/license.txt 

The license is included in /usr/share/doc, but it's not called "copyright", 
but "EULA-GoogleEarth-en.txt" partially because that's what it's called in 
the distribution, and partially because it's not even a copyright license, 
but a EULA. There is actually *no* grant of any copyright permissions, 
only "use" rights (which can't actually be restricted as much as the EULA 
tries to make it sound like, but...). But anyway, I suppose I could make 
the "copyright" file a link to this.

> * Remove the executable permission from .so

This is doable.

>   * Install a changelog file (why not the same as googleearth-package)

Not sure that's a good idea, since the same (or different!) 
googleearth-package version(s) could generate the same or different 
versions of googleearth package, but the googleearth binary package is 
versioned only using the upstream version number... I'll have to think 
about this one.

> There are some small issues left but this would be great to have at least
> an almost clean package.

Thanks for the suggestions. I don't have a ton of time to work on this right 
now, so patches would probably speed things up. Otherwise, I'll get to this 
stuff eventually. =)

-- 
Wesley J. Landaker <[EMAIL PROTECTED]> <xmpp:[EMAIL PROTECTED]>
OpenPGP FP: 4135 2A3B 4726 ACC5 9094  0097 F0A9 8A4C 4CD6 E3D2

Attachment: pgpWIOj45kQka.pgp
Description: PGP signature

Reply via email to