If we have a clear list of tasks to complete or decisions to make, maybe we can spread the effort among available time.
One of these is:
[ ] How to depend on a git project that has an .ipkg file, but no sirdi configuration file?
For concreteness, let's say the package dependencies are: A --[ depends on]---> B --[dep on] --> C, D, E.
We're developing A, while B,C, and D are outside our control (but fine to assume, say, they're on github).
While it may make a developer's life hard to maintain an explicit transitive dependency on C, D, and E, it might be impossible for them to introduce a sirdi configuration file into B for whatever reasons.
Nonetheless, sirdi should be able to cope with this situation, and the fact that sirdi is itself in this situation demonstrates that.
What would it take for sirdi to package itself?
If we have a clear list of tasks to complete or decisions to make, maybe we can spread the effort among available time.
One of these is:
.ipkgfile, but nosirdiconfiguration file? For concreteness, let's say the package dependencies are:A --[ depends on]---> B --[dep on] --> C, D, E. We're developingA, whileB,C, andDare outside our control (but fine to assume, say, they're on github). While it may make a developer's life hard to maintain an explicit transitive dependency onC,D, andE, it might be impossible for them to introduce a sirdi configuration file intoBfor whatever reasons. Nonetheless, sirdi should be able to cope with this situation, and the fact that sirdi is itself in this situation demonstrates that.