On 2022/05/05 18:45, George Rosamond wrote:
> Had some issues with py-yaml since it's a RUN_DEPEND for another port I'm
> working on, so updated.
>
> Diff attached.
>
> * bumped to 6.0 and dropped REVISION
> * dropped ${MODPY_WANTLIB} from WANTLIB as per `make port-lib-depends-check`
> output
> * fixed for default python3
> * removed whitespace in pkg/DESCR that portcheck barked about
>
> It's a DEPEND for a bunch of other ports, but didn't check those (yet).
two dependent ports are currently stuck on py 2.7
security/floss ("Automatically extract obfuscated strings from malware")
current release is still using python 2.7 (devel code supports py3, no
idea how ready it is https://github.com/mandiant/flare-floss/)
databases/mongodb where it's used in the build system
options are
#1 keep things as-is if we can manage it (i.e. no major issue needing
fixing with the py-yaml version, and no other port starts requiring a
newer version)
#2 split into py2-yaml and py-yaml, keeping the existing version in py2-yaml
#3 get the other ports updated or removed
I prefer #1 while trying to do #3, with #2 as a last resort ..
Based on offlist discussions I think that is likely to be ok with the
program you're wanting to port.
