[GRASS-dev] [GRASS GIS] #2560: Various typo fixes
GRASS GIS
trac at osgeo.org
Sun Feb 1 09:42:49 PST 2015
#2560: Various typo fixes
-----------------------+----------------------------------------------------
Reporter: sebastic | Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone: 7.0.0
Component: Docs | Version: svn-releasebranch70
Resolution: fixed | Keywords: patch
Platform: All | Cpu: Unspecified
-----------------------+----------------------------------------------------
Comment(by sebastic):
Replying to [comment:2 wenzeslaus]:
> It does not seem to me that there is any way to run these checks on the
source code. Is there some other easy way to run it?
The easier way to use lintian is to include it in the Debian package build
process. To support lintian-overrides you need to add dh_lintian calls to
the rules file. The following change was added to the official Debian
package maintained by the Debian GIS team for example:
http://anonscm.debian.org/cgit/pkg-
grass/grass.git/commit/?id=55bbe45b9881321ce3fb4dda3728d2a8abe7c3a1
I suggest you include dh_lintian in the upstream GRASS packaging on
Launchpad. This patch should work on the current grass70_release_debian
bzr branch (revision 45):
{{{
=== modified file 'rules'
--- rules 2014-08-11 09:11:22 +0000
+++ rules 2015-02-01 17:29:31 +0000
@@ -232,6 +232,7 @@
dh_installdocs -i
dh_install -i
dh_link -i
+ dh_lintian -i
dh_strip -i
dh_compress -i
dh_fixperms -i
@@ -254,6 +255,7 @@
dh_installmenu -a
dh_installman -p$(PKG_NAME) debian/$(BASE_NAME).1 -a
dh_link -a
+ dh_lintian -a
dh_python2
dh_python2 /usr/lib/$(BASE_NAME)/gui/
dh_strip -a
}}}
After the package build process is completed you run lintian on the
.changes file produced by the build. You can do this by default by
including a pbuilder hook for lintian as documented in the Debian GIS
Policy:
http://pkg-grass.alioth.debian.org/policy/packaging.html#git-pbuilder-
hooks
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2560#comment:3>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list