Hi,
On Wed, 20 Nov 2019, Felix Lechner wrote:
> There are many motivations:
Among those motivations, which one is the one that triggered this process
and which one are there as "additional benefits" that you could identify
to justify the change?
> 1. Shortens tag names.
I don't see that as a
On Wed, Nov 20, 2019 at 09:55:04AM -0800, Felix Lechner wrote:
[...]
> For example, the tag
> 'debian-copyright-file-uses-obsolete-national-encoding' might become
> 'national-encoding@debian/copyright'.
>
> There are many motivations:
>
> 1. Shortens tag names.
I do not see how that is a good
Hello Felix,
Thanks to you and others for working on this.
On Wed 20 Nov 2019 at 09:55AM -08, Felix Lechner wrote:
> For example, the tag
> 'debian-copyright-file-uses-obsolete-national-encoding' might become
> 'national-encoding@debian/copyright'.
>
> [...]
>
> The change is technically easy.
Quoting Felix Lechner (2019-11-20 18:55:04)
> I am about to introduce private namespaces for tags. Many tags already
> point to the check that issued them. (For those who don't know, a
> 'check' in Lintian is a module that issues a tag.) Namespaces would
> formalize the relationship.
>
> For
Hi,
The Lintian team has been working hard to make Lintian better. Some
call it a policy enforcer, but from our perspective Lintian just
provides friendly packaging advice for the benefit of maintainers.
A pending change may affect anyone who looks at Lintian's output. We
would like to get your
5 matches
Mail list logo
