Should I use “apt-get remove” or “apt-get purge”?apt-get or aptitudevirtualenv type tool for...

...and then she held the gun

TiKZ won't graph 1/sqrt(x)

Will users know a CardView is clickable?

How to write a nice frame challenge?

How useful is the GRE Exam?

How to search for Android apps without ads?

Why can't I craft scaffolding in Minecraft 1.14?

My student in one course asks for paid tutoring in another course. Appropriate?

Is there a term for someone whose preferred policies are a mix of Left and Right?

Is the infant mortality rate among African-American babies in Youngstown, Ohio greater than that of babies in Iran?

How can this shape perfectly cover a cube?

Testing thermite for chemical properties

How to ask if I can mow my neighbor's lawn

How did the European Union reach the figure of 3% as a maximum allowed deficit?

Cut power on a remote Raspberry Pi 3 via another raspi

Is swap gate equivalent to just exchanging the wire of the two qubits?

How to avoid offending original culture when making conculture inspired from original

How do credit card companies know what type of business I'm paying for?

Are there examples of rowers who also fought?

On George Box, Galit Shmueli and the scientific method?

Time at 1G acceleration to travel 100000 light years

How can I maintain game balance while allowing my player to craft genuinely useful items?

Leveraging cash for buying car

How to make a villain when your PCs are villains?



Should I use “apt-get remove” or “apt-get purge”?


apt-get or aptitudevirtualenv type tool for apt-get?dpkg sees them, but apt-get can't remove them?apt-get purge does not uninstall completelyUbuntu use compiled package instead of apt-getWhen and why should I use apt-get update?Syncing AIDE and apt-getRemoving 1 package wants to remove system packages AptRemove package and installed dependencies with apt-getHow does the purge command know where to look to delete package config files?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







48















For uninstalling an app (or package) should I use apt-get remove package-name or apt-get purge package-name?



What is advantage of any of them to other one?










share|improve this question































    48















    For uninstalling an app (or package) should I use apt-get remove package-name or apt-get purge package-name?



    What is advantage of any of them to other one?










    share|improve this question



























      48












      48








      48


      14






      For uninstalling an app (or package) should I use apt-get remove package-name or apt-get purge package-name?



      What is advantage of any of them to other one?










      share|improve this question
















      For uninstalling an app (or package) should I use apt-get remove package-name or apt-get purge package-name?



      What is advantage of any of them to other one?







      apt package-management






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited May 1 '14 at 16:48









      derobert

      77.2k8168227




      77.2k8168227










      asked Mar 9 '14 at 18:44









      RahmaniRahmani

      4151415




      4151415






















          3 Answers
          3






          active

          oldest

          votes


















          41














          If you have customized the package/software at all, either by editing the config files directly, or via a GUI, you may want to keep your customizations. Usually in Unix/Linux systems, configurations are saved in text files, even if the configuration/customization is done via the GUI.



          Each Debian binary deb package has a list of files which it identifies as config files. dpkg, and thus apt honor this identification when removing packages, and also on upgrades. By default apt/dpkg will not remove config files on package removal. You have to request a purge. On upgrade it will ask you to choose between the current version and the new version (if they differ) before overwriting config files. Even in that case, it saves a copy of the original file. Here Debian is trying to help you, based on the assumption that your config files may contain valuable information.



          So, if you have not configured the package, or you don't want to keep your configurations, you can use apt-get purge.



          If you do keep the config files, then if/when you reinstall the package, Debian will attempt to reuse the saved configuration information. If the version of the package you are trying to (re)install has config files that conflict with the configuration files that are already installed, it will again ask you before overwriting, as it does on upgrade.



          Minor comment: If you have removed the package and later want to remove the config files,it used to be the case that apt would not remove the config files if the package was not installed. However, for some years now, running apt-get purge will remove config files even if the package is no longer installed.



          This was fixed in the 0.8.0~pre1 version of apt, released on Fri, 13 Aug 2010, or possibly in the 0.8.15~exp1 version of apt, released Fri, 10 Jun 2011. See Debian Bug Report: apt-get --purge does not work as expected, dated 24th June 2002.






          share|improve this answer





















          • 1





            Are these equivalent: apt-get remove --purge APP VS apt-get purge APP?

            – mini
            Jul 26 '14 at 8:18






          • 1





            @mini: Yes. Quote from the apt-get man page, "remove --purge is equivalent to the purge command."

            – Faheem Mitha
            Jul 26 '14 at 8:39











          • if you have removed the package and later want to remove the config files, you will need to call dpkg directly, because apt will not remove the config files if the package is no longer installed. Does it mean that apt-get purge will not remove config files after apt-get remove has been executed?

            – Anmol Singh Jaggi
            Mar 6 '16 at 13:32













          • @AnmolSinghJaggi This part is actually incorrect and out of date. I meant to change it before. I'm changing it now.

            – Faheem Mitha
            Mar 6 '16 at 15:10











          • @FaheemMitha Okay!

            – Anmol Singh Jaggi
            Mar 6 '16 at 15:14



















          26














          From the man page of apt-get:



             remove
          remove is identical to install except that packages are removed
          instead of installed. Note that removing a package leaves its
          configuration files on the system. If a plus sign is appended to the
          package name (with no intervening space), the identified package
          will be installed instead of removed.

          purge
          purge is identical to remove except that packages are removed and
          purged (any configuration files are deleted too).


          I would tend to use purge if you tend to not want to keep any configuration files around.






          share|improve this answer































            4














            purge remove configuration files of your packages, but remove keep configuration files of your package.



            But advantages or disadvantages: It's related to your system, your packages, your machine, install it or not, and so on.






            share|improve this answer
























              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
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f118880%2fshould-i-use-apt-get-remove-or-apt-get-purge%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              41














              If you have customized the package/software at all, either by editing the config files directly, or via a GUI, you may want to keep your customizations. Usually in Unix/Linux systems, configurations are saved in text files, even if the configuration/customization is done via the GUI.



              Each Debian binary deb package has a list of files which it identifies as config files. dpkg, and thus apt honor this identification when removing packages, and also on upgrades. By default apt/dpkg will not remove config files on package removal. You have to request a purge. On upgrade it will ask you to choose between the current version and the new version (if they differ) before overwriting config files. Even in that case, it saves a copy of the original file. Here Debian is trying to help you, based on the assumption that your config files may contain valuable information.



              So, if you have not configured the package, or you don't want to keep your configurations, you can use apt-get purge.



              If you do keep the config files, then if/when you reinstall the package, Debian will attempt to reuse the saved configuration information. If the version of the package you are trying to (re)install has config files that conflict with the configuration files that are already installed, it will again ask you before overwriting, as it does on upgrade.



              Minor comment: If you have removed the package and later want to remove the config files,it used to be the case that apt would not remove the config files if the package was not installed. However, for some years now, running apt-get purge will remove config files even if the package is no longer installed.



              This was fixed in the 0.8.0~pre1 version of apt, released on Fri, 13 Aug 2010, or possibly in the 0.8.15~exp1 version of apt, released Fri, 10 Jun 2011. See Debian Bug Report: apt-get --purge does not work as expected, dated 24th June 2002.






              share|improve this answer





















              • 1





                Are these equivalent: apt-get remove --purge APP VS apt-get purge APP?

                – mini
                Jul 26 '14 at 8:18






              • 1





                @mini: Yes. Quote from the apt-get man page, "remove --purge is equivalent to the purge command."

                – Faheem Mitha
                Jul 26 '14 at 8:39











              • if you have removed the package and later want to remove the config files, you will need to call dpkg directly, because apt will not remove the config files if the package is no longer installed. Does it mean that apt-get purge will not remove config files after apt-get remove has been executed?

                – Anmol Singh Jaggi
                Mar 6 '16 at 13:32













              • @AnmolSinghJaggi This part is actually incorrect and out of date. I meant to change it before. I'm changing it now.

                – Faheem Mitha
                Mar 6 '16 at 15:10











              • @FaheemMitha Okay!

                – Anmol Singh Jaggi
                Mar 6 '16 at 15:14
















              41














              If you have customized the package/software at all, either by editing the config files directly, or via a GUI, you may want to keep your customizations. Usually in Unix/Linux systems, configurations are saved in text files, even if the configuration/customization is done via the GUI.



              Each Debian binary deb package has a list of files which it identifies as config files. dpkg, and thus apt honor this identification when removing packages, and also on upgrades. By default apt/dpkg will not remove config files on package removal. You have to request a purge. On upgrade it will ask you to choose between the current version and the new version (if they differ) before overwriting config files. Even in that case, it saves a copy of the original file. Here Debian is trying to help you, based on the assumption that your config files may contain valuable information.



              So, if you have not configured the package, or you don't want to keep your configurations, you can use apt-get purge.



              If you do keep the config files, then if/when you reinstall the package, Debian will attempt to reuse the saved configuration information. If the version of the package you are trying to (re)install has config files that conflict with the configuration files that are already installed, it will again ask you before overwriting, as it does on upgrade.



              Minor comment: If you have removed the package and later want to remove the config files,it used to be the case that apt would not remove the config files if the package was not installed. However, for some years now, running apt-get purge will remove config files even if the package is no longer installed.



              This was fixed in the 0.8.0~pre1 version of apt, released on Fri, 13 Aug 2010, or possibly in the 0.8.15~exp1 version of apt, released Fri, 10 Jun 2011. See Debian Bug Report: apt-get --purge does not work as expected, dated 24th June 2002.






              share|improve this answer





















              • 1





                Are these equivalent: apt-get remove --purge APP VS apt-get purge APP?

                – mini
                Jul 26 '14 at 8:18






              • 1





                @mini: Yes. Quote from the apt-get man page, "remove --purge is equivalent to the purge command."

                – Faheem Mitha
                Jul 26 '14 at 8:39











              • if you have removed the package and later want to remove the config files, you will need to call dpkg directly, because apt will not remove the config files if the package is no longer installed. Does it mean that apt-get purge will not remove config files after apt-get remove has been executed?

                – Anmol Singh Jaggi
                Mar 6 '16 at 13:32













              • @AnmolSinghJaggi This part is actually incorrect and out of date. I meant to change it before. I'm changing it now.

                – Faheem Mitha
                Mar 6 '16 at 15:10











              • @FaheemMitha Okay!

                – Anmol Singh Jaggi
                Mar 6 '16 at 15:14














              41












              41








              41







              If you have customized the package/software at all, either by editing the config files directly, or via a GUI, you may want to keep your customizations. Usually in Unix/Linux systems, configurations are saved in text files, even if the configuration/customization is done via the GUI.



              Each Debian binary deb package has a list of files which it identifies as config files. dpkg, and thus apt honor this identification when removing packages, and also on upgrades. By default apt/dpkg will not remove config files on package removal. You have to request a purge. On upgrade it will ask you to choose between the current version and the new version (if they differ) before overwriting config files. Even in that case, it saves a copy of the original file. Here Debian is trying to help you, based on the assumption that your config files may contain valuable information.



              So, if you have not configured the package, or you don't want to keep your configurations, you can use apt-get purge.



              If you do keep the config files, then if/when you reinstall the package, Debian will attempt to reuse the saved configuration information. If the version of the package you are trying to (re)install has config files that conflict with the configuration files that are already installed, it will again ask you before overwriting, as it does on upgrade.



              Minor comment: If you have removed the package and later want to remove the config files,it used to be the case that apt would not remove the config files if the package was not installed. However, for some years now, running apt-get purge will remove config files even if the package is no longer installed.



              This was fixed in the 0.8.0~pre1 version of apt, released on Fri, 13 Aug 2010, or possibly in the 0.8.15~exp1 version of apt, released Fri, 10 Jun 2011. See Debian Bug Report: apt-get --purge does not work as expected, dated 24th June 2002.






              share|improve this answer















              If you have customized the package/software at all, either by editing the config files directly, or via a GUI, you may want to keep your customizations. Usually in Unix/Linux systems, configurations are saved in text files, even if the configuration/customization is done via the GUI.



              Each Debian binary deb package has a list of files which it identifies as config files. dpkg, and thus apt honor this identification when removing packages, and also on upgrades. By default apt/dpkg will not remove config files on package removal. You have to request a purge. On upgrade it will ask you to choose between the current version and the new version (if they differ) before overwriting config files. Even in that case, it saves a copy of the original file. Here Debian is trying to help you, based on the assumption that your config files may contain valuable information.



              So, if you have not configured the package, or you don't want to keep your configurations, you can use apt-get purge.



              If you do keep the config files, then if/when you reinstall the package, Debian will attempt to reuse the saved configuration information. If the version of the package you are trying to (re)install has config files that conflict with the configuration files that are already installed, it will again ask you before overwriting, as it does on upgrade.



              Minor comment: If you have removed the package and later want to remove the config files,it used to be the case that apt would not remove the config files if the package was not installed. However, for some years now, running apt-get purge will remove config files even if the package is no longer installed.



              This was fixed in the 0.8.0~pre1 version of apt, released on Fri, 13 Aug 2010, or possibly in the 0.8.15~exp1 version of apt, released Fri, 10 Jun 2011. See Debian Bug Report: apt-get --purge does not work as expected, dated 24th June 2002.







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited 1 hour ago

























              answered Mar 9 '14 at 18:55









              Faheem MithaFaheem Mitha

              23.7k1887139




              23.7k1887139








              • 1





                Are these equivalent: apt-get remove --purge APP VS apt-get purge APP?

                – mini
                Jul 26 '14 at 8:18






              • 1





                @mini: Yes. Quote from the apt-get man page, "remove --purge is equivalent to the purge command."

                – Faheem Mitha
                Jul 26 '14 at 8:39











              • if you have removed the package and later want to remove the config files, you will need to call dpkg directly, because apt will not remove the config files if the package is no longer installed. Does it mean that apt-get purge will not remove config files after apt-get remove has been executed?

                – Anmol Singh Jaggi
                Mar 6 '16 at 13:32













              • @AnmolSinghJaggi This part is actually incorrect and out of date. I meant to change it before. I'm changing it now.

                – Faheem Mitha
                Mar 6 '16 at 15:10











              • @FaheemMitha Okay!

                – Anmol Singh Jaggi
                Mar 6 '16 at 15:14














              • 1





                Are these equivalent: apt-get remove --purge APP VS apt-get purge APP?

                – mini
                Jul 26 '14 at 8:18






              • 1





                @mini: Yes. Quote from the apt-get man page, "remove --purge is equivalent to the purge command."

                – Faheem Mitha
                Jul 26 '14 at 8:39











              • if you have removed the package and later want to remove the config files, you will need to call dpkg directly, because apt will not remove the config files if the package is no longer installed. Does it mean that apt-get purge will not remove config files after apt-get remove has been executed?

                – Anmol Singh Jaggi
                Mar 6 '16 at 13:32













              • @AnmolSinghJaggi This part is actually incorrect and out of date. I meant to change it before. I'm changing it now.

                – Faheem Mitha
                Mar 6 '16 at 15:10











              • @FaheemMitha Okay!

                – Anmol Singh Jaggi
                Mar 6 '16 at 15:14








              1




              1





              Are these equivalent: apt-get remove --purge APP VS apt-get purge APP?

              – mini
              Jul 26 '14 at 8:18





              Are these equivalent: apt-get remove --purge APP VS apt-get purge APP?

              – mini
              Jul 26 '14 at 8:18




              1




              1





              @mini: Yes. Quote from the apt-get man page, "remove --purge is equivalent to the purge command."

              – Faheem Mitha
              Jul 26 '14 at 8:39





              @mini: Yes. Quote from the apt-get man page, "remove --purge is equivalent to the purge command."

              – Faheem Mitha
              Jul 26 '14 at 8:39













              if you have removed the package and later want to remove the config files, you will need to call dpkg directly, because apt will not remove the config files if the package is no longer installed. Does it mean that apt-get purge will not remove config files after apt-get remove has been executed?

              – Anmol Singh Jaggi
              Mar 6 '16 at 13:32







              if you have removed the package and later want to remove the config files, you will need to call dpkg directly, because apt will not remove the config files if the package is no longer installed. Does it mean that apt-get purge will not remove config files after apt-get remove has been executed?

              – Anmol Singh Jaggi
              Mar 6 '16 at 13:32















              @AnmolSinghJaggi This part is actually incorrect and out of date. I meant to change it before. I'm changing it now.

              – Faheem Mitha
              Mar 6 '16 at 15:10





              @AnmolSinghJaggi This part is actually incorrect and out of date. I meant to change it before. I'm changing it now.

              – Faheem Mitha
              Mar 6 '16 at 15:10













              @FaheemMitha Okay!

              – Anmol Singh Jaggi
              Mar 6 '16 at 15:14





              @FaheemMitha Okay!

              – Anmol Singh Jaggi
              Mar 6 '16 at 15:14













              26














              From the man page of apt-get:



                 remove
              remove is identical to install except that packages are removed
              instead of installed. Note that removing a package leaves its
              configuration files on the system. If a plus sign is appended to the
              package name (with no intervening space), the identified package
              will be installed instead of removed.

              purge
              purge is identical to remove except that packages are removed and
              purged (any configuration files are deleted too).


              I would tend to use purge if you tend to not want to keep any configuration files around.






              share|improve this answer




























                26














                From the man page of apt-get:



                   remove
                remove is identical to install except that packages are removed
                instead of installed. Note that removing a package leaves its
                configuration files on the system. If a plus sign is appended to the
                package name (with no intervening space), the identified package
                will be installed instead of removed.

                purge
                purge is identical to remove except that packages are removed and
                purged (any configuration files are deleted too).


                I would tend to use purge if you tend to not want to keep any configuration files around.






                share|improve this answer


























                  26












                  26








                  26







                  From the man page of apt-get:



                     remove
                  remove is identical to install except that packages are removed
                  instead of installed. Note that removing a package leaves its
                  configuration files on the system. If a plus sign is appended to the
                  package name (with no intervening space), the identified package
                  will be installed instead of removed.

                  purge
                  purge is identical to remove except that packages are removed and
                  purged (any configuration files are deleted too).


                  I would tend to use purge if you tend to not want to keep any configuration files around.






                  share|improve this answer













                  From the man page of apt-get:



                     remove
                  remove is identical to install except that packages are removed
                  instead of installed. Note that removing a package leaves its
                  configuration files on the system. If a plus sign is appended to the
                  package name (with no intervening space), the identified package
                  will be installed instead of removed.

                  purge
                  purge is identical to remove except that packages are removed and
                  purged (any configuration files are deleted too).


                  I would tend to use purge if you tend to not want to keep any configuration files around.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Mar 9 '14 at 18:47









                  slmslm

                  261k72561707




                  261k72561707























                      4














                      purge remove configuration files of your packages, but remove keep configuration files of your package.



                      But advantages or disadvantages: It's related to your system, your packages, your machine, install it or not, and so on.






                      share|improve this answer




























                        4














                        purge remove configuration files of your packages, but remove keep configuration files of your package.



                        But advantages or disadvantages: It's related to your system, your packages, your machine, install it or not, and so on.






                        share|improve this answer


























                          4












                          4








                          4







                          purge remove configuration files of your packages, but remove keep configuration files of your package.



                          But advantages or disadvantages: It's related to your system, your packages, your machine, install it or not, and so on.






                          share|improve this answer













                          purge remove configuration files of your packages, but remove keep configuration files of your package.



                          But advantages or disadvantages: It's related to your system, your packages, your machine, install it or not, and so on.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Mar 9 '14 at 20:04









                          PersianGulfPersianGulf

                          7,16843663




                          7,16843663






























                              draft saved

                              draft discarded




















































                              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.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f118880%2fshould-i-use-apt-get-remove-or-apt-get-purge%23new-answer', 'question_page');
                              }
                              );

                              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







                              Popular posts from this blog

                              Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

                              Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

                              Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...