Re: poetry-core changes license location

[Greg Troxel <gdt%lexort.com@localhost>]

Thomas Klausner <wiz%netbsd.org@localhost> writes:

> On Tue, Sep 23, 2025 at 12:13:33AM +0100, Greg Troxel wrote:
>> Module Name:	pkgsrc
>> Committed By:	gdt
>> Date:		Tue Sep 23 00:13:33 UTC 2025
>> 
>> Modified Files:
>> 	pkgsrc/devel/py-unpaddedbase64: PLIST
>> 
>> Log Message:
>> devel/py-unpaddedbase64: Fix PLIST for python tool brownian motion
>
> poetry-core has done in 2.2.1 what py-setuptools did in 78 (or was it
> 82?), move the license files to a /licenses/ directory.

I must have missed the mail to tech-pkg about this :-)  But seriously,
a mechanical edit should have been part of the branch that was merged.
Maybe when we have hg, where I hear that branches are fundamentally better!

> So the fix is to update the PLIST (as you did, thanks), depend on
> poetry-core>=2.2.1 and bump PKGREVISION.

But really seriously, given how unstable poettry is, we should have a
devel/py-poetry/build.mk that will depend on a new enough version, so we
don't have to open-code a version everywhere.

As usual, I think it's important to require new-enough version, but it's
perfectly ok if old versions that might have worked are excluded.  My
belief is that the only reasonable approach is to keep everything
updated more or less in sync, and while it's good to ensure correctness
for those that don't, there's no need for optimality.