From Andrius Merkys@21:1/5 to Felix Lechner on Wed Dec 8 08:00:01 2021
Hi Felix,
On 2021-12-08 00:26, Felix Lechner wrote:
Do those two tag descriptions read the same? [1][2]
Lintian's code distinguishes between both [3] but their names and descriptions seem extremely similar to me. What am I missing, please?
Thanks!
Both of these tags report the same problem, only
libapp-perl-package-name is Perl-specific, while library-package-name-for-application is generic (from what I read).
Maybe libapp-perl-package-name could be merged into library-package-name-for-application since Perl-specific tag has only a sentence on Perl library names. Nevertheless retaining the sentence on
Perl's App:: hierarchy is a good idea. I have stumbled into libapp-perl-package-name recently, and having App:: hierarchy described
helped me a lot.
From Felix Lechner@21:1/5 to merkys@debian.org on Tue Dec 14 20:00:02 2021
Hi Andrius,
On Tue, Dec 7, 2021 at 10:53 PM Andrius Merkys <merkys@debian.org> wrote:
Both of these tags report the same problem
Maybe libapp-perl-package-name could be merged into library-package-name-for-application
Thank you for the explanation! The Perl App specific tag has a much
higher priority (E vs I) and affects only four sources (vs 897) so I
think I will keep them separate until someone has a better idea.
From Andrius Merkys@21:1/5 to Felix Lechner on Wed Dec 15 17:00:02 2021
Hi Felix,
On 2021-12-14 20:20, Felix Lechner wrote:
On Tue, Dec 7, 2021 at 10:53 PM Andrius Merkys <merkys@debian.org> wrote:
Both of these tags report the same problem
Maybe libapp-perl-package-name could be merged into
library-package-name-for-application
Thank you for the explanation! The Perl App specific tag has a much
higher priority (E vs I) and affects only four sources (vs 897) so I
think I will keep them separate until someone has a better idea.
Oh, right, I did not look at the priority! Surely if priorities are
different these tags should be kept separate.