3

I wanted to update most of the stuff on my FreeBSD system, so I was going to perform a pkg upgrade. I noticed that one of the listed new packages to be installed was Wayland; I'm not interested in having Wayland on my system, and I'm curious as to what's trying to install it. I assume it's a new dependency introduced by one of my many (many) packages being upgraded.

Is there any built in, approved, or otherwise straightforward way of determining which of my updated packages would cause Wayland to be installed on my system without actually updating those packages?

0

You can come up with right incantation of pkg rquery, but the cheap way I'm using is running pkg install on the package that I'm suspecting for pulling in the undesired one.

  • Maybe you want to add --dry-run option. – uzsolt Jan 16 at 8:13
  • Not really, pkg always asks if I want to continue, after showing the work plan. – arrowd Jan 16 at 8:16
  • 1
    But with --dry-run works as a normal (non-root) user (without it doesn't). And you don't need answer if you want only the dependencies (and can use it in a script). – uzsolt Jan 16 at 12:34
  • pkg upgrade --dry-run | awk '{if ($NF~/UPGRADED/) {output=1; next}; if (output==1) {if ($0~/^\t/) {print} else {exit}}}' | tr -d '\t' | awk -F ':' '{print $1}' | xargs -I % -L 1 sh -c 'echo %; pkg upgrade --dry-run %;' Looks like a lot of things want to introduce Wayland. Sigh. – Hammer Bro. Jan 16 at 18:22

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.