Re: Fwd: Re: Gramps Version 3.4.6
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/02/2013 11:43 PM, gregor herrmann wrote:
> On Sat, 02 Nov 2013 22:33:46 +0100, Ross Gammon wrote:
>
>> That also helped me fix the next lintian warning by guessing
>> that under the "rm", a "cp debian/gramps.xpm
>> debian//gramps/usr/share/pixmaps/" would put the menu icon in
>> the correct place.
>
> This works but is not very idiomatic; just putting
>
> debian/gramps.xpm usr/share/pixmaps/
>
> into a file debian/gramps.install (which is used by dh_install)
> should do what you want.
>
>
> Cheers, gregor
>
Thanks Gregor,
That caused me to re-read the maintainers guide on files in the debian
directory, and I was able to do a big tidy up of old redundant files
while I was at it.
That just left me with my mime types issue.
The lintian warnings looked like this:
E: gramps: package-contains-mime-cache-file usr/share/mime/XMLnamespaces
....
As suggested by the upstream INSTALL file, I enabled packager mode in
configure with an override:
override_dh_auto_configure:
dh_auto_configure -- --enable-packager-mode
This made the lintian warning go away.
This seems to bypass the update-mime-database command in the relevant
Makefile.am file. The upstream INSTALL file says this should be copied
to the postinst & postrm script.
So I put:
if [ -x /usr/sbin/update-mime-database ]; then
update-mime-database /usr/share/mime
fi
in gramps.postinst.debhelper & postrm, only to have "gbp buildpackage"
stomp all over my manual changes!!!
So I have spent some time reading & googling with no luck. How do you
incorporate manual changes to the maintainer scripts with the
automatic ones? Or if this is a common thing to do: is there a way to
get debhelper to add the "update-mime-database" to postinst & postrm
automatically?
Cheers,
Ross
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSfVgUAAoJEFP+e72miRD8pUoP/3uPfio8Uq02Kt7QF1Tn2qEr
Yar3d18vGp4KDfROUznCz0OWMtZOAZ3VO7+Agrkp6LvJkqIYjVzOZRiLquP6o5TD
iClHGcxxwiVBAxJwwnxnPHLxHIMx/nA4kDzPv2uBvo6D0EB+1R66kWEDFG/At7uz
yRj4qmeTBUMfrLJHDv48kFvh06D6U3MVjyIHAJY98vXaUPoQ04pBNcK5TnhsdZKd
/TYUsnI91a8LKsjitokj/S5bdBdRYAzo9vWpzKrg+bWicW2IqzSq6HS9JkYDPKj9
pheTxnlc0iOeSrYsYUtL1qKjIunS5f2lnzzaRnI3N9R3ILg+S3yIID5OOW6PCswS
KFjZTrnhwchj5YLTMhjaPVB6PFmLBsqCt9cUxvOIevs5Mz6cpgbV8g8pHRGNjens
Uexd1j7m0EIlS/U9z389XSRMahh6OeBF3qdI1wHLbotIWzrdLKXt3EDH3X0Y6HqJ
jZobONJpeb5fDAr3mnoULk0XSeMJBFO7MpGkPlQgeZW1Koqw5NZXDwfd5zSPKH3Y
+xbfltlz7TLUMzVtNoJeXWUkEQZqh0Cx5nPMKh6WQv80OGx9I2a6nTznUV1YsBzX
1mpa/D09gvOpkPxKTawI8mUlDPzWPsbWF9gKf/tKEHHr4YTvNhgjXXJodn1+lD3M
dJFXn5DMgz2DuOB7Lpoh
=x45Y
-----END PGP SIGNATURE-----
Reply to: