John W. Parent

@SMillerDev I believe I have either responded to or addressed your concerns/comments and this PR is ready for another round of review feedback.

@SMillerDev @fahasch Just wanted to circle back on this to keep things moving forward, please let me know what I can do to promote the progressions of this MR.

@SMillerDev Apologies for the delay, I've been OOO for the past week. I have addressed the requested changes unrelated to upstreaming the customizations I make in this MR and believe...

> If there is a mailing list archive link, I think that would be good to add as reference. Otherwise this conversation will have to do. @SMillerDev I've been looking...

@SMillerDev Last I understood these changes were ready for the upstream a few weeks ago, are there remaining blockers? What can we do to move this PR along and prevent...

@spackbot re-run pipeline

@alalazo this requires you to approve before we can merge

Gitlab CI tests paths with spaces well enough I don't think we need to bother here unless something specific comes up in the future, which can/should be handled as @alalazo...

> @johnwparent do you have plans to come back to this PR or should we close? I have plans to come back to this concept pending a conversation about expected...

> leaving in the conflicts(+icu) seems reasonable to me for now and can be removed in a separate PR once icu is buildable on Windows https://github.com/spack/spack/pull/45547 is up and building...