4 ms·
Our ideal is that if a subscriber is using it, we can sign up its maintainer. The Tidelift platform is built on an OSS project called libraries.io which support
by hp 8y ago
Our ideal is that if a subscriber is using it, we can sign up its maintainer. The Tidelift platform is built on an OSS project called libraries.io which supports many package managers: https://libraries.io/platforms https://libraries.io/platforms
Here's what's involved in adding more:
https://github.com/librariesio/libraries.io/blob/master/docs/add-a-package-manager.md https://github.com/librariesio/libraries.io/blob/master/docs...
- 0xcde4c3db 8y agoI work on a product that uses Buildroot, which doesn't really act like a "package manager" in the sense that libraries.io seems to want. We also have a handful of FOSS projects that are just copied into our tree and applied on top of the base system. Is there any anticipation of support for that kind of situation?
- hp 8y agoI think there's a clear mapping of the Tidelift model to this, and there's also some customer demand from people building embedded systems. As a practical matter it's a bit different from what we built first, both in terms of what customers are looking for / who the customers are, and in terms of the technical details of how we'd analyze dependencies. So we don't have support for it yet. But I would like to figure it out when we have enough team bandwidth.