On Wednesday, November 2, 2016 6:47:32 PM CET Pavel Raiskup wrote: > On Wednesday, November 2, 2016 1:38:57 PM CET Stephen Gallagher wrote: > > On 11/02/2016 01:09 PM, Stephen Gallagher wrote: > > > On 11/02/2016 12:51 PM, Pavel Raiskup wrote: > > >> Consider we have package 'foo-libs' that provides set of libraries. > > >> > > >> How do I get all dependant packages (for batch rebuild of dependencies after > > >> package update)? Something which takes soft dependencies into account, too. > > >> > > >> Some packages might depend on 'foo-libs' explicitly, some depend on soname > > >> (implicitly), some depend on particular file within package (say > > >> /usr/libexec/libfoohelper). > > >> > > >> Is there facility within 'dnf repoquery' that gives ultimate answer? I can do > > >> sub-queries later do pick the important rebuild candidates. > > >> > > >> Also, I would be curious about "ultimate" repoquery to get list of SOURCE > > >> dependants, e.g. on 'foo-devel'. > > >> > > > > > > > > > `dnf repoquery --enablerepo=*source --whatrequires foo-libs --all-deps` should > > > be what you're asking for. > > > > > > > > > > Minor typo: s/--all-deps/--alldeps/ > > Thanks! It is what I'm looking for. > > OTOH, it is not yet completely as good as it could be: > > <mock-chroot> sh-4.3# dnf repoquery --whatrequires python3-progress --alldeps > Last metadata expiration check: 0:00:00 ago on Wed Nov 02 18:44:33 2016 CET. > devassistant-core-0:0.11.2-7.fc25.noarch > > But: > > <mock-chroot> sh-4.3# dnf repoquery --whatrecommends python3-progress > Last metadata expiration check: 0:00:00 ago on Wed Nov 02 18:45:04 2016 CET. > copr-cli-0:1.57-1.fc26.noarch > > I don't have much examples with soft deps, so I'm not able to check what > happends if you put --alldeps and some package was under --whatsuggests > category. Related rhbz#1358245 and rhbz#1391917 filed. Pavel _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
