On Gentoo is there a way to find a list of installed packages which doesn't have other packages depended on them?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












7















On Gentoo, is there a way to find a list of installed packages which doesn't have other packages depended on them (so called leaf packages)? Or, is there analog of pkg-orphan FreeBSD utility?










share|improve this question




























    7















    On Gentoo, is there a way to find a list of installed packages which doesn't have other packages depended on them (so called leaf packages)? Or, is there analog of pkg-orphan FreeBSD utility?










    share|improve this question


























      7












      7








      7


      1






      On Gentoo, is there a way to find a list of installed packages which doesn't have other packages depended on them (so called leaf packages)? Or, is there analog of pkg-orphan FreeBSD utility?










      share|improve this question
















      On Gentoo, is there a way to find a list of installed packages which doesn't have other packages depended on them (so called leaf packages)? Or, is there analog of pkg-orphan FreeBSD utility?







      package-management gentoo emerge






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Aug 15 '12 at 0:01









      Gilles

      531k12810631592




      531k12810631592










      asked Oct 2 '11 at 9:37









      AlexDAlexD

      61369




      61369




















          2 Answers
          2






          active

          oldest

          votes


















          6














          That's what emerge --pretend --depclean does. It looks for packages that are:



          • not depended upon by other ebuilds, and

          • neither in world nor system sets

          It's a good idea to run emaint --check world to find (and later fix) potential problems with your world file before a depclean.



          Other useful tools: Gentoo maintenance






          share|improve this answer

























          • In my case, packages which I'm interested in (these perl modules from my other question) are all in world file.

            – AlexD
            Oct 2 '11 at 11:24






          • 2





            When you put stuff in world, it means "I depend on this". I.e. you are the dependency. Remove the packages that you don't explicitly need from your world file. When you emerge things you don't explicitly need, use the --oneshot option.

            – Mat
            Oct 2 '11 at 11:28











          • Adding to the previous comment by Mat: A proper command-line way to remove such packages from world is emerge --deselect package_atom, where package_atom can be simply the name of package (for more, see man portage).

            – rozcietrzewiacz
            Oct 2 '11 at 13:13











          • These packages are installed by puppet recipe so using --oneshot will require modifying puppet sources, and I need these packages included in world file in production anyway so they won't be removed by regular depclean (these packages are dependencies of large web application which is not properly packaged yet). But right now I need to clean these packages from test system and removing these packages by hand from world file (or from system) is exactly task which I'm trying to avoid.

            – AlexD
            Oct 7 '11 at 7:19











          • You can't have it both ways - tell the system they are required, then ask it for them to be cleaned up automatically. You need to track what you're doing. Sets will help a bit, but as you said in another comment it's not bullet-proof. You could also simply record all your emerge actions (with a simple wrapper) and use that to backtrack your changes.

            – Mat
            Oct 7 '11 at 7:22


















          2














          If you want to see what packages in the @world set are not also dependencies of other installed packages, you can run emerge --pretend --depclean @world (or emerge -pc @world). Also note that if you try to remove a package using emerge --depclean atom (instead of emerge --unmerge atom), portage will only remove the package if nothing else depends on it.






          share|improve this answer























          • This does not work (anymore?) emerge --pretend --depclean @world returns emerge: the given set 'world' does not support unmerge operations

            – Jonas Stein
            Jan 2 at 16:10










          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%2f21886%2fon-gentoo-is-there-a-way-to-find-a-list-of-installed-packages-which-doesnt-have%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          6














          That's what emerge --pretend --depclean does. It looks for packages that are:



          • not depended upon by other ebuilds, and

          • neither in world nor system sets

          It's a good idea to run emaint --check world to find (and later fix) potential problems with your world file before a depclean.



          Other useful tools: Gentoo maintenance






          share|improve this answer

























          • In my case, packages which I'm interested in (these perl modules from my other question) are all in world file.

            – AlexD
            Oct 2 '11 at 11:24






          • 2





            When you put stuff in world, it means "I depend on this". I.e. you are the dependency. Remove the packages that you don't explicitly need from your world file. When you emerge things you don't explicitly need, use the --oneshot option.

            – Mat
            Oct 2 '11 at 11:28











          • Adding to the previous comment by Mat: A proper command-line way to remove such packages from world is emerge --deselect package_atom, where package_atom can be simply the name of package (for more, see man portage).

            – rozcietrzewiacz
            Oct 2 '11 at 13:13











          • These packages are installed by puppet recipe so using --oneshot will require modifying puppet sources, and I need these packages included in world file in production anyway so they won't be removed by regular depclean (these packages are dependencies of large web application which is not properly packaged yet). But right now I need to clean these packages from test system and removing these packages by hand from world file (or from system) is exactly task which I'm trying to avoid.

            – AlexD
            Oct 7 '11 at 7:19











          • You can't have it both ways - tell the system they are required, then ask it for them to be cleaned up automatically. You need to track what you're doing. Sets will help a bit, but as you said in another comment it's not bullet-proof. You could also simply record all your emerge actions (with a simple wrapper) and use that to backtrack your changes.

            – Mat
            Oct 7 '11 at 7:22















          6














          That's what emerge --pretend --depclean does. It looks for packages that are:



          • not depended upon by other ebuilds, and

          • neither in world nor system sets

          It's a good idea to run emaint --check world to find (and later fix) potential problems with your world file before a depclean.



          Other useful tools: Gentoo maintenance






          share|improve this answer

























          • In my case, packages which I'm interested in (these perl modules from my other question) are all in world file.

            – AlexD
            Oct 2 '11 at 11:24






          • 2





            When you put stuff in world, it means "I depend on this". I.e. you are the dependency. Remove the packages that you don't explicitly need from your world file. When you emerge things you don't explicitly need, use the --oneshot option.

            – Mat
            Oct 2 '11 at 11:28











          • Adding to the previous comment by Mat: A proper command-line way to remove such packages from world is emerge --deselect package_atom, where package_atom can be simply the name of package (for more, see man portage).

            – rozcietrzewiacz
            Oct 2 '11 at 13:13











          • These packages are installed by puppet recipe so using --oneshot will require modifying puppet sources, and I need these packages included in world file in production anyway so they won't be removed by regular depclean (these packages are dependencies of large web application which is not properly packaged yet). But right now I need to clean these packages from test system and removing these packages by hand from world file (or from system) is exactly task which I'm trying to avoid.

            – AlexD
            Oct 7 '11 at 7:19











          • You can't have it both ways - tell the system they are required, then ask it for them to be cleaned up automatically. You need to track what you're doing. Sets will help a bit, but as you said in another comment it's not bullet-proof. You could also simply record all your emerge actions (with a simple wrapper) and use that to backtrack your changes.

            – Mat
            Oct 7 '11 at 7:22













          6












          6








          6







          That's what emerge --pretend --depclean does. It looks for packages that are:



          • not depended upon by other ebuilds, and

          • neither in world nor system sets

          It's a good idea to run emaint --check world to find (and later fix) potential problems with your world file before a depclean.



          Other useful tools: Gentoo maintenance






          share|improve this answer















          That's what emerge --pretend --depclean does. It looks for packages that are:



          • not depended upon by other ebuilds, and

          • neither in world nor system sets

          It's a good idea to run emaint --check world to find (and later fix) potential problems with your world file before a depclean.



          Other useful tools: Gentoo maintenance







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jan 2 at 18:49









          Anthony Geoghegan

          7,66543954




          7,66543954










          answered Oct 2 '11 at 10:35









          MatMat

          39k8117125




          39k8117125












          • In my case, packages which I'm interested in (these perl modules from my other question) are all in world file.

            – AlexD
            Oct 2 '11 at 11:24






          • 2





            When you put stuff in world, it means "I depend on this". I.e. you are the dependency. Remove the packages that you don't explicitly need from your world file. When you emerge things you don't explicitly need, use the --oneshot option.

            – Mat
            Oct 2 '11 at 11:28











          • Adding to the previous comment by Mat: A proper command-line way to remove such packages from world is emerge --deselect package_atom, where package_atom can be simply the name of package (for more, see man portage).

            – rozcietrzewiacz
            Oct 2 '11 at 13:13











          • These packages are installed by puppet recipe so using --oneshot will require modifying puppet sources, and I need these packages included in world file in production anyway so they won't be removed by regular depclean (these packages are dependencies of large web application which is not properly packaged yet). But right now I need to clean these packages from test system and removing these packages by hand from world file (or from system) is exactly task which I'm trying to avoid.

            – AlexD
            Oct 7 '11 at 7:19











          • You can't have it both ways - tell the system they are required, then ask it for them to be cleaned up automatically. You need to track what you're doing. Sets will help a bit, but as you said in another comment it's not bullet-proof. You could also simply record all your emerge actions (with a simple wrapper) and use that to backtrack your changes.

            – Mat
            Oct 7 '11 at 7:22

















          • In my case, packages which I'm interested in (these perl modules from my other question) are all in world file.

            – AlexD
            Oct 2 '11 at 11:24






          • 2





            When you put stuff in world, it means "I depend on this". I.e. you are the dependency. Remove the packages that you don't explicitly need from your world file. When you emerge things you don't explicitly need, use the --oneshot option.

            – Mat
            Oct 2 '11 at 11:28











          • Adding to the previous comment by Mat: A proper command-line way to remove such packages from world is emerge --deselect package_atom, where package_atom can be simply the name of package (for more, see man portage).

            – rozcietrzewiacz
            Oct 2 '11 at 13:13











          • These packages are installed by puppet recipe so using --oneshot will require modifying puppet sources, and I need these packages included in world file in production anyway so they won't be removed by regular depclean (these packages are dependencies of large web application which is not properly packaged yet). But right now I need to clean these packages from test system and removing these packages by hand from world file (or from system) is exactly task which I'm trying to avoid.

            – AlexD
            Oct 7 '11 at 7:19











          • You can't have it both ways - tell the system they are required, then ask it for them to be cleaned up automatically. You need to track what you're doing. Sets will help a bit, but as you said in another comment it's not bullet-proof. You could also simply record all your emerge actions (with a simple wrapper) and use that to backtrack your changes.

            – Mat
            Oct 7 '11 at 7:22
















          In my case, packages which I'm interested in (these perl modules from my other question) are all in world file.

          – AlexD
          Oct 2 '11 at 11:24





          In my case, packages which I'm interested in (these perl modules from my other question) are all in world file.

          – AlexD
          Oct 2 '11 at 11:24




          2




          2





          When you put stuff in world, it means "I depend on this". I.e. you are the dependency. Remove the packages that you don't explicitly need from your world file. When you emerge things you don't explicitly need, use the --oneshot option.

          – Mat
          Oct 2 '11 at 11:28





          When you put stuff in world, it means "I depend on this". I.e. you are the dependency. Remove the packages that you don't explicitly need from your world file. When you emerge things you don't explicitly need, use the --oneshot option.

          – Mat
          Oct 2 '11 at 11:28













          Adding to the previous comment by Mat: A proper command-line way to remove such packages from world is emerge --deselect package_atom, where package_atom can be simply the name of package (for more, see man portage).

          – rozcietrzewiacz
          Oct 2 '11 at 13:13





          Adding to the previous comment by Mat: A proper command-line way to remove such packages from world is emerge --deselect package_atom, where package_atom can be simply the name of package (for more, see man portage).

          – rozcietrzewiacz
          Oct 2 '11 at 13:13













          These packages are installed by puppet recipe so using --oneshot will require modifying puppet sources, and I need these packages included in world file in production anyway so they won't be removed by regular depclean (these packages are dependencies of large web application which is not properly packaged yet). But right now I need to clean these packages from test system and removing these packages by hand from world file (or from system) is exactly task which I'm trying to avoid.

          – AlexD
          Oct 7 '11 at 7:19





          These packages are installed by puppet recipe so using --oneshot will require modifying puppet sources, and I need these packages included in world file in production anyway so they won't be removed by regular depclean (these packages are dependencies of large web application which is not properly packaged yet). But right now I need to clean these packages from test system and removing these packages by hand from world file (or from system) is exactly task which I'm trying to avoid.

          – AlexD
          Oct 7 '11 at 7:19













          You can't have it both ways - tell the system they are required, then ask it for them to be cleaned up automatically. You need to track what you're doing. Sets will help a bit, but as you said in another comment it's not bullet-proof. You could also simply record all your emerge actions (with a simple wrapper) and use that to backtrack your changes.

          – Mat
          Oct 7 '11 at 7:22





          You can't have it both ways - tell the system they are required, then ask it for them to be cleaned up automatically. You need to track what you're doing. Sets will help a bit, but as you said in another comment it's not bullet-proof. You could also simply record all your emerge actions (with a simple wrapper) and use that to backtrack your changes.

          – Mat
          Oct 7 '11 at 7:22













          2














          If you want to see what packages in the @world set are not also dependencies of other installed packages, you can run emerge --pretend --depclean @world (or emerge -pc @world). Also note that if you try to remove a package using emerge --depclean atom (instead of emerge --unmerge atom), portage will only remove the package if nothing else depends on it.






          share|improve this answer























          • This does not work (anymore?) emerge --pretend --depclean @world returns emerge: the given set 'world' does not support unmerge operations

            – Jonas Stein
            Jan 2 at 16:10















          2














          If you want to see what packages in the @world set are not also dependencies of other installed packages, you can run emerge --pretend --depclean @world (or emerge -pc @world). Also note that if you try to remove a package using emerge --depclean atom (instead of emerge --unmerge atom), portage will only remove the package if nothing else depends on it.






          share|improve this answer























          • This does not work (anymore?) emerge --pretend --depclean @world returns emerge: the given set 'world' does not support unmerge operations

            – Jonas Stein
            Jan 2 at 16:10













          2












          2








          2







          If you want to see what packages in the @world set are not also dependencies of other installed packages, you can run emerge --pretend --depclean @world (or emerge -pc @world). Also note that if you try to remove a package using emerge --depclean atom (instead of emerge --unmerge atom), portage will only remove the package if nothing else depends on it.






          share|improve this answer













          If you want to see what packages in the @world set are not also dependencies of other installed packages, you can run emerge --pretend --depclean @world (or emerge -pc @world). Also note that if you try to remove a package using emerge --depclean atom (instead of emerge --unmerge atom), portage will only remove the package if nothing else depends on it.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 15 '12 at 15:38









          Jonathan CallenJonathan Callen

          33018




          33018












          • This does not work (anymore?) emerge --pretend --depclean @world returns emerge: the given set 'world' does not support unmerge operations

            – Jonas Stein
            Jan 2 at 16:10

















          • This does not work (anymore?) emerge --pretend --depclean @world returns emerge: the given set 'world' does not support unmerge operations

            – Jonas Stein
            Jan 2 at 16:10
















          This does not work (anymore?) emerge --pretend --depclean @world returns emerge: the given set 'world' does not support unmerge operations

          – Jonas Stein
          Jan 2 at 16:10





          This does not work (anymore?) emerge --pretend --depclean @world returns emerge: the given set 'world' does not support unmerge operations

          – Jonas Stein
          Jan 2 at 16:10

















          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%2f21886%2fon-gentoo-is-there-a-way-to-find-a-list-of-installed-packages-which-doesnt-have%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

          How to check contact read email or not when send email to Individual?

          Displaying single band from multi-band raster using QGIS

          How many registers does an x86_64 CPU actually have?