Hi Riku, Jakub Wilk wrote: > * Riku Voipio <riku.voi...@iki.fi>, 2015-08-24, 11:00: > >These obsolete urls are already checked with duck[1][2]. I think > >what would make sense would be to make lintian recommend duck. > >Then lintian can run duck if it has been installed. > > Leaving aside privacy issues, that would make Lintian output > dependent on external world, which would be against its design > constraints: > https://lintian.debian.org/manual/section-1.3.html > > So I'm afraid we can't run duck, at least not by default.
I think a nice place to have duck being run automatically via some per-user configuration is the debuild script from devscripts. It runs lintian by default after each build and has a hook for running further such scripts. Unfortunately this hook is not run inside the source directory but in its parent. So it needs a bit of shell code around it. And debuild exits if the final error code is not zero. So it also needs "true" as last command. I currently use this: DEBUILD_LINTIAN_HOOK="if [ -d %p-%u ]; then cd %p-%u; duck; elif [ -d %p ]; then cd %p; duck; else exit 1; fi; true" (Simon: Maybe this is suitable as hint for the duck man page?) Another way is to use wrapper tools like these: https://anonscm.debian.org/cgit/pkg-perl/packages/pkg-perl-tools.git/tree/examples/check-build https://packages.debian.org/source/experimental/check-all-the-things Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
