On 2012-09-17 13:49, Niels Thykier wrote:
* Where do contrib checks install their data files?
A suggestion could be:
root/vendors/contrib/X/...
and have Lintian special case it.
Looking at the code needed to do this special casing, we might as well
just restore the root/data dir
* Niels Thykier ni...@thykier.net, 2012-10-11, 23:22:
How will overrides play with contrib checks? [I had a user who wanted
to add an override for lintian4python, though there's currently no way
to do that.]
I think adding them to the standard overrides file will just work.
Do you have a
On 2012-10-12 11:45, Jakub Wilk wrote:
* Niels Thykier ni...@thykier.net, 2012-10-11, 23:22:
How will overrides play with contrib checks? [I had a user who wanted
to add an override for lintian4python, though there's currently no
way to do that.]
I think adding them to the standard overrides
* Niels Thykier ni...@thykier.net, 2012-10-12, 21:54:
[0] I have a distinct memory of seeing spurious unused-override tags
in early stage of lintian4python development. But maybe my memory is
playing tricks on me.
Depending on when you did this testing last, your memory may be true.
At the
* Niels Thykier ni...@thykier.net, 2012-09-17, 13:49:
I have devised a prototype implementation[1], which should demonstrate
how this could be implemented with relatively few changes on top of the
master branch.
In the prototype,
1 the command line argument is --contrib-check X
2 if
On 2012-10-11 22:42, Jakub Wilk wrote:
* Niels Thykier ni...@thykier.net, 2012-09-17, 13:49:
I have devised a prototype implementation[1], which should demonstrate
how this could be implemented with relatively few changes on top of
the master branch.
In the prototype,
1 the command line
Package: lintian
Version: 2.5.10.1
Followup-For: Bug #359059
Long ago, Russ Allbery may have written:
[...]
Stefano Zacchiroli z...@debian.org writes:
This tension is clear as well. Still, I believe that inhibiting
macro-areas of Debian to have their own tests is too constraining in
7 matches
Mail list logo
