the submission rules state not to declare deps of deps.
whatever tool you use, way you can't get away from the need to rebuild other packages from time to time. Usually if there is a major version change so the api/abi may changel and that may require rebuilding some trees.
One issue with declaring all sub deps in a package is maintainers having to keep track of all the sub deps and potential optional deps. increasing the work for the maintainers, and making it very difficult to stay up to date, due to daisy chain effects of one lib changing it's dep, causing half the repo needing to be updated. That is not a sustainable way to operate, as the sbo admins would be flooded with updates all the time, and due to the release cycle, changes would propagate over weeks. Our current method of only listing direct deps, and if something breaks then fix it is more manageable than forcing cascading updates if one lib changes it's deps.
on approach is rebuild and see if it works. if not, rebuild tree. you can use tools like sqg to generate dep trees, just bare in mind any "optional deps".
regards Tim _______________________________________________ SlackBuilds-users mailing list [email protected] https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
