how to remove everything deps that installed with a program?

how to remove everything it installed on a piece of Software?
Code:
udo pkg install shotcut
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 46 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
    blas: 3.11.0
    eigen: 3.4.0_1
    freexl: 1.0.6
    frei0r: 1.8.0_1
    frei0r-plugins: 1.8.0_1
    frei0r-plugins-gavl: 1.8.0
    frei0r-plugins-opencv: 1.8.0
    gavl: 1.4.0_4
    gdal: 3.6.2_3
    gdcm: 3.0.21
    geos: 3.11.1
    gsm: 1.0.19
    lapack: 3.11.0
    lapacke: 3.11.0
    libavif: 0.11.1
    libdc1394: 2.2.6
    libgeotiff: 1.7.1_3
    libkml: 1.3.0_25
    librttopo: 1.1.0
    minizip: 1.2.11
    mlt7: 7.14.0
    movit: 1.6.3
    netcdf: 4.9.0_2
    opencl: 3.0.12
    opencv: 4.6.0_5
    opusfile: 0.12
    postgresql13-client: 13.10
    proj: 9.2.0,1
    protobuf: 3.21.12,1
    py39-numpy: 1.24.1,1
    qhull: 8.0.2_1,1
    qt5-declarative: 5.15.8p21
    qt5-multimedia: 5.15.8p1
    qt5-opengl: 5.15.8p157
    qt5-quickcontrols2: 5.15.8p7
    qt5-websockets: 5.15.8p2
    sdl2_image: 2.6.3
    sfcgal: 1.4.1_3
    shapelib: 1.5.0
    shotcut: 22.06.23
    sox: 14.4.2.20210509_1
    spatialite: 5.0.1_5
    swhplugins: 0.4.17
    uriparser: 0.9.6
    vid.stab: 0.98.2
    xerces-c3: 3.2.4

Number of packages to be installed: 46

The process will require 418 MiB more space.
86 MiB to be downloaded.
remove it
Code:
sudo pkg remove  shotcut
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
    shotcut: 22.06.23

Number of packages to be removed: 1

The operation will free 12 MiB.

Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling shotcut-22.06.23...
[1/1] Deleting files for shotcut-22.06.23: 100%
Building the Shared MIME-Info database cache
Generating GTK icon cache for /usr/local/share/icons/hicolor
Building cache database of MIME types
 
pkg autoremove

autoremove
Delete packages which were automatically installed as dependen-
cies and are not required any more.

pkg autoremove

autoremove an autoremove, they should either send a message like linux or fix it to remove them deps at the same time.

Delete packages which were automatically installed as dependen-
cies and are not required any more.
it has an autoremove where is the message like debian Linux etc. ? someone is dropping the ball. I'll try that when I get into that system
 
And pkg clean -a for the cache.

??
Code:
man pkg
man pkg-clean
cache isn't installed programs
A cache -- pronounced CASH -- is hardware or software that is used to store something, usually data, temporarily in a computing environment.
that pkg -a to remove cache makes no since but okay I'll check that out too when I get into that system.
 
And pkg clean -a for the cache.

??
Code:
man pkg
man pkg-clean
Is this really even needed to be stored on the system if it is already installed into the system and an update/upgrade to that package will just make it obsolete anyways?

edied due to it exceeds the amount of letters allowed to post at one time
Code:
The following package files will be deleted:
.........
The cleanup will free 2 GiB
 
Is this really even needed to be stored on the system if it is already installed into the system and an update/upgrade to that package will just make it obsolete anyways?
The pkg upgrade process will sometimes "reinstall" a package, minor changes that affect very little. Part of the process up pkg upgrade or pkg install is to download the binary tarballs onto the system, then determine any order dependencies then install. They get downloaded to, yes, a cache. It's default location is /var/cache/pkg and if you ls -l you'll see pkg files and symlinks to them.

In the BSD spirit of not hiding anything from you, I don't think pkg will automatically get rid of unused stuff in /var/cache/pkg, that's why almost all tutorials dealing with packages have a pkg clean or pkg autoremove step.

Note that the command is:
pkg clean -a not pkg -a. I'm assuming it's simply a typo, just making sure.

Do they absolutely need to be saved once the package is installed? Not really, but if you get rid of them (pkg clean -a), next time you do a pkg upgrade you may wind up downloading a whole bunch of them again. If you are tight on disk space, you can do a pkg clean -a to get rid of them.
 
I think the complaint was: I don't have a message that I should run autoremove after deleting packages, like cow powers in Debian.?
debian-example.jpg
 
I think the complaint was: I don't have a message that I should run autoremove after deleting packages, like cow powers in Debian.?
View attachment 15969
debian and knock offs of same. I don't run on a reg. Slackware is my main Linux/GNU, but that is where I learned about the infamous autoremove to get rid of the no longer needed packages, then asked myself why didn't you do that for me in the first place? like it's not like that is not programmable to do gezzz debain and its knock offs get it together - already :rolleyes:

and if you actually think about it calling it "autoremove" is wrong, it is not autoremoving anything because now you have to issue a sperate command, it should be "do-it-yourself-because-the-devs-are-too-lazy-to-add-that-to-the-script" but that turns out to be a rather long command. ?
 
Code:
pkg autoremove is used for removing orphan packages, which were installed
     during dependency resolution and are no longer needed.


Even with the smiling laughing emoji, your last paragraph is odd and pretty much ignores the definition autoremove.

Bottom line:
Binary packages on FreeBSD, through the pkg command, behave differently than "package" commands on Linux distributions (apt, yum, dnf, dpkg, etc). After having using both for a long time my opinion is "it's best if you embrace and understand the system you are working with; comparing/trying to bend to the way a different system works means you are going to be very disappointed."
 
Code:
pkg autoremove is used for removing orphan packages, which were installed
     during dependency resolution and are no longer needed.


Even with the smiling laughing emoji, your last paragraph is odd and pretty much ignores the definition autoremove.

Bottom line:
Binary packages on FreeBSD, through the pkg command, behave differently than "package" commands on Linux distributions (apt, yum, dnf, dpkg, etc). After having using both for a long time my opinion is "it's best if you embrace and understand the system you are working with; comparing/trying to bend to the way a different system works means you are going to be very disappointed."
Automatic:
Acting or operating in a manner essentially independent of external influence or control.

remove:
  1. To move from a place or position occupied.
  2. To transfer or convey from one place to another.
  3. To take off

using #3 for remove then shorten the two words putting them together forming the new word "Autoremove" thereby independent of external influence being a user to remove something. thereby the word in its structure means it is automated removal of no longer needed anything . thereby applying that word incorrectly because it now needs an external influence to remove the items. It has noting to do with understanding the system and the commands .

it is simplely pointing out the gross missue of the word becuase of its meaning that is being perverted by the devs in its usage. because someone has to intervene by issuing a command that clearly indecates it is automatic . if that were true then if anything it should tell me it already did it for me.
 
Automatic:
Acting or operating in a manner essentially independent of external influence or control.

remove:
  1. To move from a place or position occupied.
  2. To transfer or convey from one place to another.
  3. To take off

using #3 for remove then shorten the two words putting them together forming the new word "Autoremove" thereby independent of external influence being a user to remove something. thereby the word in its structure means it is automated removal of no longer needed anything . thereby applying that word incorrectly because it now needs an external influence to remove the items. It has noting to do with understanding the system and the commands .

it is simplely pointing out the gross missue of the word becuase of its meaning that is being perverted by the devs in its usage. because someone has to intervene by issuing a command that clearly indecates it is automatic . if that were true then if anything it should tell me it already did it for me.
Dude, you're starting to become annoying with this. Do a "man pkg-autoremove" and you get the text I posted. You come across as "why doesn't freebsd do this like linux".

pkg autoremove fits your warped vision; when the command is run by a user it will automatically remove packages that are not used, not depended on by any other installed packages.
Unless you are saying "if a user has to enter Yes or No it's not automatic".
 
Dude, you're starting to become annoying with this. Do a "man pkg-autoremove" and you get the text I posted. You come across as "why doesn't freebsd do this like linux".

pkg autoremove fits your warped vision; when the command is run by a user it will automatically remove packages that are not used, not depended on by any other installed packages.
Unless you are saying "if a user has to enter Yes or No it's not automatic".
dude I was being sarcastic due to the actual misuse of the meaning of automatic and the word remove being used when one actually had to issue a command to remove the items then some other dude could not wrap his head about that simple fact so I tried explaining it to him and now again?

automatic would mean that is just does it for you AUTOMATICALLY, as they are no longer needed there for the serve no real reason for being on the system other then to take up space but the devs thought why not make them remove it by issing another seperate command instead of just removing them automatically.

it is simple math here.
 
and if you actually think about it calling it "autoremove" is wrong, it is not autoremoving anything because now you have to issue a sperate command, it should be "do-it-yourself-because-the-devs-are-too-lazy-to-add-that-to-the-script" but that turns out to be a rather long command. ?
???

Automatic:
Acting or operating in a manner essentially independent of external influence or control.

remove:
  1. To move from a place or position occupied.
  2. To transfer or convey from one place to another.
  3. To take off

using #3 for remove then shorten the two words putting them together forming the new word "Autoremove" thereby independent of external influence being a user to remove something. thereby the word in its structure means it is automated removal of no longer needed anything . thereby applying that word incorrectly because it now needs an external influence to remove the items. It has noting to do with understanding the system and the commands .

it is simplely pointing out the gross missue of the word becuase of its meaning that is being perverted by the devs in its usage. because someone has to intervene by issuing a command that clearly indecates it is automatic . if that were true then if anything it should tell me it already did it for me.
I would agree if this applied to a single command that removed a single package. However, it likely that this refers to the automatic removal of multiple.

pkg autoremove fits your warped vision;
WARPED VISION

it is simple math here.
Let's not confuse the matter further by introducing mathematics into this conversation, too.
 
dude I was being sarcastic due to the actual misuse of the meaning of automatic and the word remove being used when one actually had to issue a command to remove the items then some other dude could not wrap his head about that simple fact so I tried explaining it to him and now again?

automatic would mean that is just does it for you AUTOMATICALLY, as they are no longer needed there for the serve no real reason for being on the system other then to take up space but the devs thought why not make them remove it by issing another seperate command instead of just removing them automatically.
Wrong interpretation. The tool removes automatically installed packages. Not automatically remove packages.
 
???


I would agree if this applied to a single command that removed a single package. However, it likely that this refers to the automatic removal of multiple.


WARPED VISION


Let's not confuse the matter further by introducing mathematics into this conversation, too.
even though you may or may not be joking around with that it is hard to tell as text has no inflection, other then that in the head of the reader. Sorry most people cannot transpose ideologies as metaphors.

it's simple math = it's elementary


Wrong interpretation. The tool removes automatically installed packages. Not automatically remove packages.
well, it is looking like someones(s) is wanting an intellectual debate.

in the case of Ubuntu not fbsd but perhaps them too as I just learned they use autoremove as well, developers developed a package system and leave out the logic. ( so now I am just taking this off the top of my head from past experiences as I have not done a study of it completely)

I install a package , the pkg system takes care of the dependencies (extra packages) needed to make it work. so I looks them up and tells you these too are needed then ask you do you want all of this stuff installed on your system to make that package work.

Okay, logic here, maybe they just want the single program package so ask. Okay

now user does not want that package anymore, remove it, no logic is applied nor put to question in some cases. do you want all of this other stuff no longer needed for that program to work remove too?

why do I need it? remove it.

Ubunitu ends up with what is called orphaned packages, why? then they tell you about it you have packages that have no use whatsoever on your system is you want them remove then type sudo autoremove .

begs the question what are they doing there in the first place, how did they get there, and why did you not remove them whenever I was removing packages.

yes sometimes multiple programs depend on the same dependencies, so yeah don't remove those ones, just everything else that was installed to get that one program to work that I told the system to remove,

when installing and removing programs the dependencies should come and go along with them, otherwise we end up with what is called the orphaned packages which need to be autoremoved.

when in fact they are not being removed automatically because the user has to issue a command to have it do so. If they'd have been automatically removed in the first place then no message ever would show up telling the user they need to be automatically removed.

does not matter

to say "Wrong interpretation. The tool removes automatically installed packages. Not automatically remove packages."

that is a break in logic, a twist in words, the word autoremove by the english language and its usages, to automatically remove something. regardless of how it got there.

if it removes automatically installed packages, no orphaned, and the deps being removed by the usage of the program (script) called autoremove that are left behind especially in the case of FBSD.

where they automatically installed or did someone have to tell the package system to install them along with telling the package to install the main program?

for the most part you have to agree to have the system install anything you tell it to install to be installed. Where total size is the of the complete install is being used for the determination of doing so.

Now if the main package is removed you have to use 'autoremove' to remove the deps too else they are left behind thus causing them to become what is called orphaned. So that statment is illogical. becae the deps were not automatcilly instelled, you have to yas yes to that then use automove to remove them when the main pkg is removed.

if the tool is used to remove automatically installed packages then logic states there is no need for it. if they are "automatically installed" then they should be automatically removed too when no longer needed.

the term then is being used in a contradiction to itself - actually whenever it is being used it is in a contradiction to itself because it is not automatically removing anything because a outside influence has to tell it to do so.

Hence my sarcastic statement about it that started this debate on the matter.

it's simple math , (I already explained the metaphor)
 
If you are wanting to clean up, then FreeBSD has the ability to simply remove all 3rd party packages and you can start again (unlike all Linux distros).

Code:
# pkg delete -a

Keeping the base separate here is a real winner compared to Linux where it is just a cluster fsck of files.

And if you find yourself adding and removing packages a lot, then setting up a temporary jail (or chroot) is generally a good idea. Again, FreeBSD makes this much easier than Linux in that you pretty much just extract a single tarball and don't need to mount proc, sysfs or run systemd-logind, dbus and all that crud.

autoremove is sometimes only a kludge for a slightly awkward workflow.
 
even though you may or may not be joking around with that it is hard to tell as text has no inflection, other then that in the head of the reader. Sorry most people cannot transpose ideologies as metaphors.

it's simple math = it's elementary



well, it is looking like someones(s) is wanting an intellectual debate.

in the case of Ubuntu not fbsd but perhaps them too as I just learned they use autoremove as well, developers developed a package system and leave out the logic. ( so now I am just taking this off the top of my head from past experiences as I have not done a study of it completely)

I install a package , the pkg system takes care of the dependencies (extra packages) needed to make it work. so I looks them up and tells you these too are needed then ask you do you want all of this stuff installed on your system to make that package work.

Okay, logic here, maybe they just want the single program package so ask. Okay

now user does not want that package anymore, remove it, no logic is applied nor put to question in some cases. do you want all of this other stuff no longer needed for that program to work remove too?

why do I need it? remove it.

Ubunitu ends up with what is called orphaned packages, why? then they tell you about it you have packages that have no use whatsoever on your system is you want them remove then type sudo autoremove .

begs the question what are they doing there in the first place, how did they get there, and why did you not remove them whenever I was removing packages.

yes sometimes multiple programs depend on the same dependencies, so yeah don't remove those ones, just everything else that was installed to get that one program to work that I told the system to remove,

when installing and removing programs the dependencies should come and go along with them, otherwise we end up with what is called the orphaned packages which need to be autoremoved.

when in fact they are not being removed automatically because the user has to issue a command to have it do so. If they'd have been automatically removed in the first place then no message ever would show up telling the user they need to be automatically removed.

does not matter

to say "Wrong interpretation. The tool removes automatically installed packages. Not automatically remove packages."

that is a break in logic, a twist in words, the word autoremove by the english language and its usages, to automatically remove something. regardless of how it got there.

if it removes automatically installed packages, no orphaned, and the deps being removed by the usage of the program (script) called autoremove that are left behind especially in the case of FBSD.

where they automatically installed or did someone have to tell the package system to install them along with telling the package to install the main program?

for the most part you have to agree to have the system install anything you tell it to install to be installed. Where total size is the of the complete install is being used for the determination of doing so.

Now if the main package is removed you have to use 'autoremove' to remove the deps too else they are left behind thus causing them to become what is called orphaned. So that statment is illogical. becae the deps were not automatcilly instelled, you have to yas yes to that then use automove to remove them when the main pkg is removed.

if the tool is used to remove automatically installed packages then logic states there is no need for it. if they are "automatically installed" then they should be automatically removed too when no longer needed.

the term then is being used in a contradiction to itself - actually whenever it is being used it is in a contradiction to itself because it is not automatically removing anything because a outside influence has to tell it to do so.

Hence my sarcastic statement about it that started this debate on the matter.

it's simple math , (I already explained the metaphor)
You know... for what it's worth... I appreciate how much you're willing to invest in arguing semantics.
 
you know for what it's worth, I think ... most just accept as it is without question .. drones , zombies . blind compliancy . don't think, don't ask, don't question . just do,

Unless someone has the technical skills to implement change, it is best they learn the way the software works and just use it. They can save themselves a lot of hassle.

The days of consumers demanding software to change to best suit them and their use-case ended with Windows XP.
 
Back
Top