Le Tue, Nov 19, 2024 at 12:35:28PM +0100, Theo Buehler a écrit : > Brad sent me a diff for boost 1.87.0b1 to test (included at the end). As > was to be expected, it comes with significant fallout. A lot of the > damage from the 1.85 filesystem removals didn't fix itself: > > https://marc.info/?l=openbsd-ports&m=171375368020942&w=2 > > Then there's a few more API removals on top. > > Not sure what the best way to proceed would be. Some major linux distros > (arch, suse tumbleweed) and pkgsrc ship 1.86, FreeBSD has 1.85. So fixes > should be findable even if some upstreams don't seem to include them yet. > > It's going to be tedious whether we update boost in one, two, or even > three steps. At some point, people who care about these ports need to > step up and help. As far as I can tell, nobody reacted when brad sent > the 1.85 update. > > Many of the affected ports are leaves or nearly leaves and don't seem to > serve a particularly important purpose, so I would not be opposed to > landing 1.85 or 1.86 first and marking the no longer building ports > broken after a week or two, then see what's left to do for 1.87 once > it's out. > > One thing that would really help would be to prod upstreams to drop > their use of deprecated APIs before boost actually removes them. But > that means actually looking at the C++ spew and spot the deprecations > between all the other noise. > > Here's the list, with some details below.
just looking at osrm-backend it dropped the filesystem dep in https://github.com/Project-OSRM/osrm-backend/pull/6960 and https://github.com/Project-OSRM/osrm-backend/pull/6432 Landry
