On Fri, Jul 08, 2022 at 03:19:03AM +0300, Faidon Liambotis wrote: > It'd be great if the package shipped with such a symlink structure, > and/or came with instructions on how one can use this package (either > with this structure, or, if possible, without).
Upon further research, I found the following comment from upstream to another distributor (NixOS) that may be relevant: https://github.com/WebAssembly/wasi-libc/issues/269#issuecomment-1067565836 Quoting it here for posterity: > One difference between wasm-libc and other/normal software that you > might want to package is that it is designed to be used only within > the sysroot of a cross compiler. I assume you understand that and are > creating some kind of packaged sysroot or cross toolchain? Given that, > does it still make sense to be able to install/redirect headers and > libraries using the normal packaging machinery that you have? For > example, if I was packaging for linux I would not want wasm-libc to > install in the same way the normal library would (i.e. honoring the > the normal include and library paths). Best, Faidon
