InsightToolkit: new port InsightToolkit version 5.3.0, replacing InsightToolkit-devel

[nilason]

Description

Create new port InsightToolkit 5.3.0, replacing InsightToolkit-devel. Also add Python subports, along with general Portfile overhaul.

Type(s)

• bugfix
• enhancement
• security fix

Tested on

macOS 12.6.6 21G646 arm64
Xcode 14.2 14C18

Verification

Have you

• followed our Commit Message Guidelines?
• squashed and minimized your commits?
• checked that there aren't other open pull requests for the same change?
• checked your Portfile with port lint --nitpick?
• tried a full install with sudo port -vst install?
• checked that the Portfile's most important variants haven't been broken?

[macportsbot]

Notifying maintainers:
@stromnov for port InsightToolkit-devel.

[nilason]

The CI's weren't happy with two conflicting ports, I moved part of this original PR to #20400.

[nilason]

This depends on merging #20424 .

[mascguy]

It might also be worth dropping the Python 3.9 subport, for both InsightToolkit ports.

[nilason]

It might also be worth dropping the Python 3.9 subport, for both InsightToolkit ports.

I wouldn't mind. Will do.

I also plan to add to this PR, a port rename. From InsightToolkit-devel to just InsightToolkit (in the process making the former obsolete). Any thoughts on that?

[mascguy]

I also plan to add to this PR, a port rename. From InsightToolkit-devel to just InsightToolkit (in the process making the former obsolete). Any thoughts on that?

Seems reasonable.

Do you expect this port to remain at major version 5.x? Or is the plan to keep this in-sync with upstream, including updating beyond to 6.x, etc?

[nilason]

I also plan to add to this PR, a port rename. From InsightToolkit-devel to just InsightToolkit (in the process making the former obsolete). Any thoughts on that?

Seems reasonable.

Do you expect this port to remain at major version 5.x? Or is the plan to keep this in-sync with upstream, including updating beyond to 6.x, etc?

My plan is to keep InsightToolkit the latest version available (to continue with 6.x etc). If necessary – for whatever reason (like the need for InsightToolkit4 for the orfeotoolbox update) – fork and create a InsightToolkit5 and so forth.

[mascguy]

My plan is to keep InsightToolkit the latest version available (to continue with 6.x etc). If necessary – for whatever reason (like the need for InsightToolkit4 for the orfeotoolbox update) – fork and create a InsightToolkit5 and so forth.

Sounds great!

[nilason]

I addressed the issues you had. I also changed this to create a new port InsightToolkit and make InsightToolkit-devel obsolete. I added myself as co-maintainer for InsightToolkit.

Has there ever been a port named InsightToolkit and if so, did it have epoch set?

[mascguy]

I addressed the issues you had. I also changed this to create a new port InsightToolkit and make InsightToolkit-devel obsolete. I added myself as co-maintainer for InsightToolkit.

Has there ever been a port named InsightToolkit and if so, did it have epoch set?

There was at one point, but the last version was 3.16.0. And no, epoch was not set.

[mascguy]

LGTM, apart from obsolete date needed for InsightToolkit-devel.

[nilason]

Obsolete date added.

[nilason]

I addressed the issues you had. I also changed this to create a new port InsightToolkit and make InsightToolkit-devel obsolete. I added myself as co-maintainer for InsightToolkit.
Has there ever been a port named InsightToolkit and if so, did it have epoch set?

There was at one point, but the last version was 3.16.0. And no, epoch was not set.

That explains the "-devel" port for v4+ I suppose.

[nilason]

Thanks for your assistance!