
| Msg # 15081 of 15094 on ZZLI4416, Wednesday 11-04-25, 9:00 |
| From: PETER BLACKMAN |
| To: ROLAND ROSENFELD |
| Subj: Bug#1119932: Question about lrc and perl |
19: a=IkcTkHD0fZMA: AaPWxdG9OSFygR8OP8ynN0BuqzPX plus. <91dee5f9- From: peter@pblackman.plus.com On 26/10/2025 12:38, Roland Rosenfeld wrote: > 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. I've filed one now! https://bugs.debian.org/1119932 > But there is no "Perl" license, but Perl itself is under "Artistic or > GPL-1+", which I defined in debian/copyright: ... > 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? I've added the facility to list license aliases in debian/lrc.config. I use the vertical bar '|' as separator, so these lines can be cut and pasted from lrc's output. Where the same license discrepancy occurs over several files in different directories, it makes a lot of sense to just list the license pairs, rather then each file. As the Artistic or GPL-1+ | Perl issue is likely to affect other Perl packages, its included by default in version 9.0 I had been considering this feature for a while now, thanks for the nudge! Cheers, Peter --- SoupGate-Win32 v1.05 * Origin: you cannot sedate... all the things you hate (1:229/2) |
328,081 visits
(c) 1994, bbs@darkrealms.ca