-------- Forwarded Message --------
Subject: Question about lrc and perl license
Date: Sun, 26 Oct 2025 13:38:48 +0100
From: Roland Rosenfeld <[email protected]>
To: Peter Blackman <[email protected]>
Hi Peter!
I like your tool licenserecon/lrc, but I have one question about it,
where I didn't find an answer for. Since I think that it is a
misunderstanding of my side, I won't file a bug report for it.
When I run lrc in the chordpro source package, it reports:
---- cut ----
: Versions: licenserecon '8.1' licensecheck '3.3.9-1'
Parsing Source Tree ....
Reading d/copyright ....
Running licensecheck ....
d/copyright | licensecheck
Artistic or GPL-1+| GPL-1 LICENSE
Artistic or GPL-1+| Perl lib/ChordPro.pm
Artistic or GPL-1+| Perl lib/ChordPro/Config/Properties.pm
Artistic or GPL-1+| Perl lib/ChordPro/lib/Class/JSON_Object.pm
Artistic or GPL-1+| Perl
lib/ChordPro/lib/Data/Printer/Theme/Zellner.pm
Artistic or GPL-1+| Perl lib/ChordPro/lib/JSON/Relaxed.pm
Artistic or GPL-1+| Perl lib/ChordPro/res/pod/ChordPro.pod
---- cut ----
Okay, I learned, that I should whitelist the LICENSE file using
echo "LICENSE" > debian/lrc.config
But what should I do with the other files. The license in these files
tells me:
---- cut ----
Copyright 1994,2002,2020 Johan Vromans, all rights reserved.
This program is free software; you can redistribute it and/or modify it
under the same terms as Perl itself.
---- cut ----
But there is no "Perl" license, but Perl itself is under "Artistic or
GPL-1+", which I defined in debian/copyright:
---- cut ----
Files: *
Copyright: 2010-2024 Johan Vromans <[email protected]>
2010-2023 The ChordPro Team
License: Artistic or GPL-1+
---- cut ----
Is there any trick to make lrc feel happy about "Perl" being some
kind of an alias for "Artistic or GPL-1+" or do I have to change
debian/copyright?
Greetings
Roland
