Advertisement
Guest User

Untitled

a guest
Mar 22nd, 2018
67
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.05 KB | None | 0 0
  1. # depclean
  2.  
  3. * Always study the list of packages to be cleaned for any obvious
  4. * mistakes. Packages that are part of the world set will always
  5. * be kept. They can be manually added to this set with
  6. * `emerge --noreplace <atom>`. Packages that are listed in
  7. * package.provided (see portage(5)) will be removed by
  8. * depclean, even if they are part of the world set.
  9. *
  10. * As a safety measure, depclean will not remove any packages
  11. * unless *all* required dependencies have been resolved. As a
  12. * consequence of this, it often becomes necessary to run
  13. * `emerge --update --newuse --deep @world` prior to depclean.
  14.  
  15. Calculating dependencies... done!
  16. >>> Calculating removal order...
  17.  
  18. >>> These are the packages that would be unmerged:
  19.  
  20. dev-util/scons
  21. selected: 2.4.1
  22. protected: none
  23. omitted: none
  24.  
  25. All selected packages: =dev-util/scons-2.4.1
  26.  
  27. >>> 'Selected' packages are slated for removal.
  28. >>> 'Protected' and 'omitted' packages will not be removed.
  29.  
  30. Would you like to unmerge these packages? [Yes/No] ^CInterrupted.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement