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
As mentioned in #1913 (comment), we could consider re-structuring linux-like stuff, i.e., Android and emscripten so that we could de-duplicate some items and remove make it more consistent.
In particular, we could move android under linux rather than just linux_like (since it actually runs Linux and should have most things in common), and we could also move emscripten up from linux_like to unix if that wouldn't create too much duplication.
If we do both, we'd stop needing the linux_like level at all. If we do just one or the other, I'd say it should be to move android under linux.
Not directly related, but I am working with uclibc, and considering whether to put together a PR to move uclibc under linux-like/linux, which is where I felt it belonged anyway. Reading the git history, it seems unclear to me why it was kept out of what was then not-bsd. This probably isn't the correct forum to ask, but would a PR to move uclibc be considered?
If this isn't an ok spot to ask, then my apologies! Please feel free to point me at a better spot.
Reacted by Jubilee, Lance Fredrickson and Trevor Gross
I think that moving uclibc around would be fine, if it's not been moved already (the question was asked over 2 years ago...).
I think that Emscripten should definitely be moved out of "Linux-like", or whatever other refactoring. It definitely tries to pare everything down to the narrow edge of "POSIX-only", which means common Linux extensions, even ones implemented by multiple other BSD OS, because they're actually part of fundamental things like ELF, don't fly on it. Thus it is creating more code duplication to have things duplicated between Linux-and-Android-but-not-Emscripten. I also notice a lot of PRs to add stuff to the libc API surface for the Linuxes tend to fail on Emscripten, specifically.
Activity
joshtriplett commentedon Oct 7, 2020
In particular, we could move android under
linuxrather than justlinux_like(since it actually runs Linux and should have most things in common), and we could also move emscripten up fromlinux_liketounixif that wouldn't create too much duplication.If we do both, we'd stop needing the
linux_likelevel at all. If we do just one or the other, I'd say it should be to move android underlinux.skrap commentedon Nov 9, 2020
Not directly related, but I am working with uclibc, and considering whether to put together a PR to move uclibc under linux-like/linux, which is where I felt it belonged anyway. Reading the git history, it seems unclear to me why it was kept out of what was then not-bsd. This probably isn't the correct forum to ask, but would a PR to move uclibc be considered?
If this isn't an ok spot to ask, then my apologies! Please feel free to point me at a better spot.
workingjubilee commentedon Mar 6, 2023
I think that moving uclibc around would be fine, if it's not been moved already (the question was asked over 2 years ago...).
I think that Emscripten should definitely be moved out of "Linux-like", or whatever other refactoring. It definitely tries to pare everything down to the narrow edge of "POSIX-only", which means common Linux extensions, even ones implemented by multiple other BSD OS, because they're actually part of fundamental things like ELF, don't fly on it. Thus it is creating more code duplication to have things duplicated between Linux-and-Android-but-not-Emscripten. I also notice a lot of PRs to add stuff to the libc API surface for the Linuxes tend to fail on Emscripten, specifically.