List Dependencies of Pending `pkg upgrade`
Clash Royale CLAN TAG#URR8PPP
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?
package-management freebsd upgrade dependencies pkg
add a comment |
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?
package-management freebsd upgrade dependencies pkg
add a comment |
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?
package-management freebsd upgrade dependencies pkg
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?
package-management freebsd upgrade dependencies pkg
package-management freebsd upgrade dependencies pkg
edited Jan 16 at 0:25
Jeff Schaller
40.8k1056129
40.8k1056129
asked Jan 15 at 23:47
Hammer Bro.Hammer Bro.
1183
1183
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494703%2flist-dependencies-of-pending-pkg-upgrade%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
add a comment |
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
add a comment |
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.
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.
answered Jan 16 at 7:02
arrowdarrowd
41339
41339
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
add a comment |
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
Maybe you want to add
--dry-run
option.– uzsolt
Jan 16 at 8:13
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
Not really,
pkg
always asks if I want to continue, after showing the work plan.– arrowd
Jan 16 at 8:16
1
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
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
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
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494703%2flist-dependencies-of-pending-pkg-upgrade%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown