Sergey Bugaev

Darling will definitely continue — at least as a way to run x86_64 (or x86) binaries on x86_64 Linux systems. We also want to get arm64-on-arm64 binaries working (but not...

> it fails at building Ruby. Where's the error? In your log there's only a make error, not a compiler error. This usually indicates that a compiler was simply OOM-killed,...

> You need to install few missed libraries `dyld` and `abort_with_payload` that Darling developers did not include in their project. > `$ brew install dyld abort_with_payload` That's... hilarious, and that's...

Is domain name resolution the part that is not working, or is the whole internet connectivity broken? (Try connecting to an explicit IP address.)

I can't say I understand how Darling's resolver is implemented (darling-resolver calls into libresolv... or something), but from where I stand, it _should_ be calling native glibc's APIs; then everything...

At some point we wanted *an option* to toggle between "share networking with the host" and "have a Darling container run in its own network namespace". Not sure if we...

But in case of Docker we also would want for the Darling container to share networking with "the host" (i.e. the Docker container), not to create another nested namespace with...

> To give a specific example, launchd is under the ASPL, yet the project itself claims to be under the GPLv3 What [we claim](http://darlinghq.org/source-code/) is > Source code implemented as...

> Where there might be certain issues with non-GPL code calling into GPL code is any code that makes BSD/Darwin syscalls > The possible problem arises because non-GPL code included...

> Folks, if this is _the_ issue that prevents me from 'apt-get'-ing your code from Ubuntu central repositories, please do fix it. Why do you think that's the case? Has...