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 07:15:35AM +0100, Greg Troxel wrote:

>> 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.
>
> Doesn't help, the PLIST needs to be fixed manually anyway.

It still helps; while we'd still need to fix PLIST, there'd be one less
line to maintain.

>> 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.
>
> They work, but they produce a different PLIST, so to produce a
> particular PLIST, we need to depend on a new-enough version of
> poetry-core.

Sure, that makes sense in this case.  I meant that pkgsrc seems to try
hard to allow building with really old deps, as long as we can't prove
they are too old, instead of taking the attitude that to build a package
things should be more or less all up to date.

> I've been watching the bulk builds - I think most of the resulting
> problems are now fixed.

Great, thanks for your diligence on this.   I think everything I have
installed is ok now too.