You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When @kinokrt was, for Release 1, originally setting up the GitHub CI pipeline (for flow, then ipc), it turned out that jemalloc was in some way incompatible with Conan 2, so he (we) instead went with for Conan 1.x for the time being. About a year later I asked him to get us to Conan 2 after all (Conan 1.x is deprecated, and e.g. Boost no longer makes new-version recipes for it; and it could get worse than that). So he did: branch conan2 for flow and ditto for ipc. It is not merged however to main x 2.
We should merge that work to main, either in a separate PR or as part of another.
Related/bonus: Boost-1.87 is currently obtained from an alternate remote (for each of flow, ipc), because it was never added to ConanCenter -- and never will be, due to the aforementioned deprecation. While the alternate remote works, it is also a kludge (involving some annoying not-short files in the source tree, at that). Having upgraded to Conan 2, going back to ConanCenter for Boost-1.87 should be very easy; and we might as well do it. It's small enough to not need a ticket (in a sense it's a style change anyway).
Priority: Conan 1.x is deprecated. The longer we go without this, the more painful it's going to be later; eventually it'll be mandatory, while the pressure will be worse.
Tactics:
Since the aforementioned unmerged work, we've added (and merged) some minor things to Flow and some to Flow-IPC; and also for Flow-IPC/ipc#143 are preparing a huge change to both Flow and Flow-IPC, including various pipeline changes. Because of the latter fact:
We could, and arguably opportunistically should, do so as part of that work; meaning get it into the same branch.
Granted, doing separate-subject PRs separately is nice for history and such. In this case, though, the Performance deep dive. ipc#143 PR, due to the way it was developed elsewhere and then mostly brought into GitHub as one large thing, throwing in the 1.x=>2(+Boost1.87) item hardly changes things. Less busy-work too.
When @kinokrt was, for Release 1, originally setting up the GitHub CI pipeline (for
flow, thenipc), it turned out that jemalloc was in some way incompatible with Conan 2, so he (we) instead went with for Conan 1.x for the time being. About a year later I asked him to get us to Conan 2 after all (Conan 1.x is deprecated, and e.g. Boost no longer makes new-version recipes for it; and it could get worse than that). So he did: branchconan2forflowand ditto foripc. It is not merged however tomainx 2.We should merge that work to
main, either in a separate PR or as part of another.Related/bonus: Boost-1.87 is currently obtained from an alternate remote (for each of flow, ipc), because it was never added to ConanCenter -- and never will be, due to the aforementioned deprecation. While the alternate remote works, it is also a kludge (involving some annoying not-short files in the source tree, at that). Having upgraded to Conan 2, going back to ConanCenter for Boost-1.87 should be very easy; and we might as well do it. It's small enough to not need a ticket (in a sense it's a style change anyway).
Priority: Conan 1.x is deprecated. The longer we go without this, the more painful it's going to be later; eventually it'll be mandatory, while the pressure will be worse.
Tactics:
Since the aforementioned unmerged work, we've added (and merged) some minor things to Flow and some to Flow-IPC; and also for Flow-IPC/ipc#143 are preparing a huge change to both Flow and Flow-IPC, including various pipeline changes. Because of the latter fact: