Le 23/12/2022 à 20:46, Tonus a écrit :
> May I suggest something like :
> for x in $(cat my_builds.txt) ; do find SBo-15.0/ -name "$x.info" grep
> "REQUIRE" {} \; ; done
This will not find indirect dependencies listed as Reverse Dependency (full) in
https://slackbuilds.org/advsearch.php
> Beware, wrote that on my phone, can't test it.
>
> Since I feel more comfortable with such one-liner I would be glad to have
> advices.
>
> Regards
>
> Le 23 décembre 2022 19:27:57 GMT+01:00, "B. Watson" <urch...@slackware.uk> a
> écrit :
>>
>>
>> On Fri, 23 Dec 2022, Alexander Verbovetsky wrote:
>>
>>> On Fri, Dec 23, 2022 at 10:28:04AM +0700, Willy Sudiarto Raharjo wrote:
>>>
>>>> libraries/leptopnica: Updated for version 1.83.0.
>>>
>>> This breaks graphics/tesseract. Can be fixed by straightforward bumping
>>> the tesseract version from 5.0.1 to 5.3.0 (the support for latest
>>> releases of leptonica is mentioned in the changelog for 5.2.0).
>>
>> Do people not even check to see if their updates break the builds that
>> depend on it?
>>
>> Open letter to all maintainers: before you submit an update, look
>> up your build using the reverse dependency search on the "Advanced
>> Search" page here: https://slackbuilds.org/advsearch.php
>>
>> For leptonica, this shows 2 builds: jbi2genc and tesseract. These
>> are exactly the ones that got broken by the update...
>>
>> *Test* the dependees with your updated build before submitting it.
>> If it breaks something, the *least* you can do is notify the
>> maintainers of the builds you're about to break. Even better if you
>> fix the breakage in their builds and *send them patches*.
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
