Re: CVS commit: pkgsrc/textproc/py-cmudict

["David H. Gutteridge" <david%gutteridge.ca@localhost>]

> Module Name:    pkgsrc
> Committed By:   adam
> Date:           Wed Feb 15 18:19:24 UTC 2023
>
> Modified Files:
>        pkgsrc/textproc/py-cmudict: Makefile distinfo
>
> Log Message:
> py-cmudict: updated to 1.0.13
>
> v1.0.13 (2022-12-19)
>
> Fix
>
> added commitizen config
> explicit ci jobs
> publish on tag v
> added release workflow
>
>
> To generate a diff of this commit:
> cvs rdiff -u -r1.2 -r1.3 pkgsrc/textproc/py-cmudict/Makefile \
>    pkgsrc/textproc/py-cmudict/distinfo

Hi Adam,

A few things about this. As you probably saw, it broke bulk builds,
since you bumped the py-importlib-metadata minimum requirement to
5.1.0, but we have 4.12.0 presently in pkgsrc. I've reverted much of
the update.

The reason I (as the package maintainer) didn't update this package to
1.0.13 was simply because there's no value in doing so. Every change
only pertains to internal project workflow automations, so while
bumping it is harmless, it doesn't gain users any advantage. (I'm not
even sure there are any users other than me, but I digress.)

I don't think the minimum dependencies the project reports are even
correct. I think they simply bump them to whatever the latest versions
are available as of the time they regenerate files on each release
(assuming that everyone is using pip and will just pull in the latest).

Now, we might well want to update py-importlib-metadata to a newer
version, but I'm not looking at that tonight, and I don't think it
should be done if just to support this package moving to .13.

Regards,

Dave