Seungmin Kim

> It sounds like that could potentially be you? It's not immediate for me in the current sense, but in a year or so if people can wait. It will...

@h-vetinari Great, thank you! I am also waiting for more potential contributors to contribute to this job. Perhaps from my own project. We can wait and see. Meanwhile, I'd thank...

Follow up from https://github.com/conda-forge/xorg-libxfixes-feedstock/pull/8#issuecomment-2351604599 @hmaarrfk I have been consistently aware of what @pkgw is trying to do (read the top part of this issue that I added and will edit...

Note that I no longer have dedicated time for development, so I cannot sit down for this in the foreseeable future. The three new recent contributions of feedstocks were because...

Thanks to the efforts of @isuruf, https://github.com/conda-forge/xorg-libxcvt-feedstock/pull/4 is an example of using the newest MinGW compiler pipeline. This can pretty much likely be the way forward to reduce the amount...

@pkgw I have updated your notes in https://github.com/conda-forge/libglvnd-feedstock/pull/2 here in the first post. One comment is that some (core) packages including libx11 itself still have legacy build code and automake1.15,...

It is likely that setting `LD_LIBRARY_PATH` will lead to having only the 32-bit libraries provisioned instead of both. There are exactly same library names targetting different architectures such as `/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0`...

> You need to run a mix of 32-bit and 64-bit applications in the same container? You can't run different containers for the different applications? I'm not sure that apptainer...

I don't have enough time now, but let's keep this open, then.

By the way, I think `--compat32` is the right option name since this may also hold for AMD ROCm.