1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
|
There are many small improvements that can be made to Debian packages
automatically. It would be great if there was an easy way for Debian developers
to apply available automatic changes.
It should be easy to add new fixers, without having to familiarize yourself
with the internals of lintian-brush. Ideally, a script written in any language
that modifies the package.
Maintainers should of course review the changes made by the tool, but they should
be able to rely on the tool making the right modifications. If the tool isn't sure
about a change (i.e. it may break the package) then it should err on the side
of caution and not make the change.
(Perhaps at some point in the future we could add a flag with the minimum
certainty of fixers to run?)
Performance
===========
lintian-brush should be fast when there is nothing that it can do. It currently
(May 2020) takes 7 seconds to run on a Samba sized tree, and just over a second
on smaller trees. That figure should ideally only go down.
Any actions that do involve making changes to the tree may take longer, and may
involve e.g. talking to other services over the network. The idea is that it's fine
for lintian-brush to take time when it's actually providing value, and to be quick
when it's not. In addition, any time a change is actually being made that should be
a one-off wait - once the fix is committed, it won't have to be made again and
the next run will be fast.
Non-goals
=========
Most things that are out of scope for lintian should be out of scope for
lintian-brush as well. In particular, updates that require changes to multiple
packages (and coordinated uploads) probably belong in a different tool.
Fixing upstream issues is out of scope, even though lintian warns about some
of those issues. Automatic fixing of these issues belongs in a
distribution-agnostic tool.
|
