- Edited
I wish moss
(or boulder
, not sure which one this should apply to) can have the ability or provide APIs to spit out the dependency graph of a package's run-time (also build-time, if possible) dependencies. This can save a lot of trouble for package maintainers, like now for Solus I need to write my own script that converts the entire eopkg-index.xml
to a huge dependency graph, and then do some graph theory magic (usually by doing topological sorting) to tell me the safe order to rebuild packages.
I also hope we can know, say after a package update and some ABI symbols were changed/deleted, what packages (i.e. its reverse dependencies) will be affected by that. In this way, package maintainers don't have to rebuild every package down the dependency tree and be confident that things won't break. This is probably more suited to include in summit/vessel/avalanche since the amount of ABI symbols can quickly get very large and likely requires a database. If doing this for every package is not possible, the ability to do a one-shot search for a single package is also enough.
Serpent OS will be "smart" in the users' eyes, therefore I hope it can also be "smart" for package maintainers.