In my last blog post about Traveling Ruby's future, I said that it's hard to democratize the development of Traveling Ruby because of System Integrity Protection (SIP). Traveling Ruby's build process relies on
DYLD_LIBRARY_PATH, which is blocked by SIP. This means that:
- Contributors that build Traveling Ruby on their own laptops, must disable SIP.
- Traveling Ruby cannot be built on many CI hosting services, such as Azure DevOps and Github Actions, because it's not possible to disable SIP there.
After some research and experimentation, I've found an alternative to
DYLD_LIBRARY_PATH, meaning that it's no longer necessary to disable SIP. This significantly changes the ability to democratize Traveling Ruby's development.