On Sat, Nov 7, 2020 at 9:48 AM Stuart Henderson <stu@spacehopper.org> wrote:
>
> Here's what I make the list of victims of removing py-numpy would be.
> Some of the ports involved aren't that important but others definitely
> are.
>
> devel/boost
> - (lots)
> games/angrydd
> games/fretsonfire
> games/singularity
> ...(snip)...
Thanks for this updated list Stuart, this was also previously
highlighted here with my thoughts on a plan at that time:
https://marc.info/?l=openbsd-ports&m=160245446411390&w=2
(although a few of the things mentioned on that thread have since been
addressed).
> For opencv, digikam and nomacs don't appear to need python parts at all,
> let alone py2, I don't think dropping py2 from there is likely to cause
> much upset.
interesting, hadn't looked at the ports with maintainers myself yet.
but will look at if maintainers don't tackle. in which case, thanks
for the hints.
>
> For boost, I don't see anything with a listed wantlib on any type of
> the boost-numpy libs. Worth a bulk (on amd64; i386 misses too much
> these days to really be a good test) to make sure but dropping that
> should be possible too I think.
That sounds great. Getting boost moved over would be a huge help. I
think it's one of the last big stumbling blocks.
> For this reason I think that we need a py2-numpy for now
I don't know if we need it just yet? I'd like to at least finish
trying to see how much stuff can be moved over. I had a rough sketch
of a plan for everything apart from some of the games to be honest so
I think we can make a lot more progress before we need a py2-numpy
port.
No comments:
Post a Comment