boost182, boost183: provide ports for new versions

[barracuda156]

Could we offer ports for new Boost versions?

[mascguy (Christopher Nielsen)]

Well, we had so many Boost ports before, that the number was unmanageable.

So we'll add a new version at some point, but it hasn't been a high priority. Particularly if the set of versions we have, are sufficient.

Do you have any ports that only work with Boost 1.82 or newer...?

[barracuda156]

Replying to mascguy:

Well, we had so many Boost ports before, that the number was unmanageable.

So we'll add a new version at some point, but it hasn't been a high priority. Particularly if the set of versions we have, are sufficient.

Do you have any ports that only work with Boost 1.82 or newer...?

There is absolutely no urgency in this, as far as my ports go; Boost 1.81 (with our patches) seems to work fine so far. Since patches were merged to upstream, likely we can drop them with a newer version, but that is no big deal.

I have set the priority to low. It is desirable to make those, but indeed no hurry here.

[artkiver (グレェ)]

WIP Portfile for boost183

[artkiver (グレェ)]

It seems as if minor modifications to the boost181 Portfile (WIP example attached) install OK? Admittedly, I am no expert in boost. I am looking into it as a dependency for graphics/usd (which is installing boost176) and noticed that it seems as if boost is in a similar state to Python, with a gazillion versions. ;-/ So, my apologies if my minor contribution isn't of much help!

[mascguy (Christopher Nielsen)]

Replying to artkiver: I am looking into it as a dependency for graphics/usd (which is installing boost176) and noticed that it seems as if boost is in a similar state to Python, with a gazillion versions.

Yep, we pruned the number of versions back to four, over the past four months. (Simply because it was becoming burdensome to maintain them all.)

So we'll add a new one eventually. But they're released so often, that it's pointless to keep creating - and supporting - each new release.

[barracuda156]

Replying to mascguy:

Replying to artkiver:

I am looking into it as a dependency for graphics/usd (which is installing boost176) and noticed that it seems as if boost is in a similar state to Python, with a gazillion versions.

Yep, we pruned the number of versions back to four, over the past few months. (Simply because it was becoming burdensome to maintain them all.)

So we'll add a new one eventually. But they're released so often, that it's pointless to keep creating - and supporting - each new release.

Well, I guess we could try a new one, as long as someone did the work? I can test PowerPC and aarch64.

[mascguy (Christopher Nielsen)]

Replying to barracuda156:

Well, I guess we could try a new one, as long as someone did the work? I can test PowerPC and aarch64.

I thought you already confirmed that you don't have a need for a newer veraion?

Meanwhile, you have a LOT of open PRs. Please focus on those, okay?

[barracuda156]

Replying to mascguy:

Replying to barracuda156:

Well, I guess we could try a new one, as long as someone did the work? I can test PowerPC and aarch64.

I thought you already confirmed that you don't have a need for a newer veraion?

I do not require Boost newer than we have for anything, correct.

Meanwhile, you have a LOT of open PRs. Please focus on those, okay?

Yeah, sure. (And I still need your assistance with 2–3 of those.)

[artkiver (グレェ)]

another WIP Portfile for boost 1.83

[artkiver (グレェ)]

Regarding the other Portfile I just attached, I tweaked it some more to get it working with python312 locally. Admittedly, I think I fudged it and the "set selected_python python311" should probably be changed at a minimum as well? tbh, I don't really understand why that would be hardcoded anyway, but there's a LOT about how MacPorts handles Python dependencies which leaves much to be desired.

Regardless, I thought I would delve into it a little bit more as I noticed some issue/PR in upstream's openusd that mentioned needing boost 1.82 and Python 3.11 so I thought would try to get a little bit further ahead of that with 1.83 and Python 3.12, but the usd MacPort is years behind upstream at the moment, and I still can't figure out why the boost PortGroup is being used there and defaulting to boost176. I'm a little out of my depth, so again my apologies if my contributions aren't of value, but I figured maybe they might be useful to others as a reference point and better than cluttering up disk space locally if nothing else?