On Fri, 2026-05-22 at 04:33 +0530, Nilesh Patra wrote: > > > On 18 May 2026 2:47:45 am IST, Andrew McMillan > <[email protected]> wrote: > > Hi, > > > > Just confirming what I've said in other places. > > > > I have reviewed the text of version 4.0 of the PHP license and can > > confirm it is a "BSD 3 Clause" variant and is now fully compatible > > with > > the Debian Free Software Guidelines, without any residual "it just > > applies to PHP itself" issues. > > Yes, I get that. The answer to my question is still not clear. > > Do you think it would be beneficial for lintian to drop tags for > perl-2 and perl-3 license? > > Can this new license retroactively make those two DFSG compatible? > > It would be non-trivial to detect for lintian the signs of PHP-4.0 > in d/copyright and selectively adopt or drop the tag, as folks may > name it differently. I'd therefore prefer for lintian to simply get > rid of these or keep them as is. > Or if thereare other ideas around this, I'm all ears.
I think you can drop them all (I assume by 'perl-2' and 'perl-3' you're really meaning 'php-2' and 'php-3'). If they are present in existing packages in Debian they're already past any gatekeeping or other imagined effect these tags might have, and if they aren't then they'll get pulled up on review by the DFSG Team and we will ask them to go upstream to switch to PHP-4. That action won't be triggered from a Lintian warning, but from the other tools we are using for license review. Cheers, Andrew. -- ---------------------------------------------------------------------- Porirua, New Zealand +64 (27) 288 6741 Why not go out on a limb? Isn't that where the fruit is? ----------------------------------------------------------------------
