Emerge packages installed

Ever been curious to find out how much space a specific package is occupying? Since a package could have its files over a number of directories, the usual du -hc command might not give the correct figure. Don't worry, equery to the rescue! Using size prints the total space used in human-readable units and lists the total number of files the package has. To get the total size in bytes use --bytes.

Here a number of USE flags are enabled in gstreamer's plugin meta-package, but it can be seen that there are other USE flags available. If an unversioned package name is passed using which it will return the path to the newest installable ebuild version. Lastly, if none of the above features of equery have provided an answer, try using which to manually search an ebuild with programs like cat , less or grep :. Equery From Gentoo Wiki.

This page contains changes which are not marked for translation. Other languages:. Note Globbing support replaced a number of older options in equery. Note This output will include optional dependencies governed by USE flags, i. A package would only be a dependency if that USE flag is active.

Warning Be aware that equery currently changes the format of the output if it is sent through a pipe. The piped format is intended to be easier to parse by tools, but it can be turned off by adding the --no-pipe option. Clean will remove all but the most recently installed version in each slot. Clean should not remove unslotted packages. Note: Most recently installed means most recent , not highest version. Run package specific actions needed to be executed after the emerge process has completed.

This usually entails configuration file setup or other similar setups that the user may wish to run. Cleans the system by removing packages that are not associated with explicitly merged packages.

Depclean works by creating the full dependency tree from the world set, then comparing it to installed packages. Packages installed, but not part of the dependency tree, will be uninstalled by depclean. See --with-bdeps for behavior with respect to build time dependencies that are not strictly required. Packages that are part of the world set will always be kept. As a consequence, it is often necessary to run emerge --update --newuse --deep world prior to depclean.

Also note that depclean may break link level dependencies, especially when the --depclean-lib-check option is disabled. Thus, it is recommended to use a tool such as revdep-rebuild 1 in order to detect such breakage. WARNING: Inexperienced users are advised to use --pretend or --ask with this option in order to see a preview of which packages will be uninstalled.

Always study the list of packages to be cleaned for any obvious mistakes. Note that packages listed in package. Depclean serves as a dependency aware version of --unmerge. When given one or more atoms, it will unmerge matched packages that have no reverse dependencies.

Use --depclean together with --verbose to show reverse dependencies. This action is implied by uninstall actions, including --depclean , --prune and --unmerge. Displays help information for emerge. Adding one of the additional arguments listed above will give you more specific help information on that subject. The internal emerge help documentation is updated more frequently than this man page; check it out if you are having problems that this man page does not help resolve. Produces a list of information to include in bug reports which aids the developers when fixing the reported problem.

Please include this information when submitting a bug report. Expanded output can be obtained with the --verbose option. This process populates the cache database that portage uses for pre-parsed lookups of package data. In order to generate cache for overlays, use --regen. Removes all but the highest installed version of a package from your system.

Use --prune together with --verbose to show reverse dependencies or with --nodeps to ignore all dependencies. Check the emerge output of the next --depclean run carefully! Use --depclean to avoid this issue. Causes portage to check and update the dependency cache of all ebuilds in the portage tree.

The cache is used to speed up searches and the building of dependency trees. This command is not recommended for rsync users as rsync updates the cache using server-side caches. If you do not know the differences between a 'rsync user' and some other user, then you are a 'rsync user' :.

Rsync users should simply run emerge --sync to regenerate the cache. After a portage update, rsync users may find it convenient to run emerge --metadata to rebuild the cache as portage does at the end of a sync operation.

In order to specify parallel --regen behavior, use the --jobs and --load-average options. If you would like to generate and distribute cache for use by others, use egencache 1. Resumes the most recent merge list that has been aborted due to an error. This re-uses the options that were given with the original command that's being resumed, and the user may also provide additional options when calling --resume.

Please note that this operation will only return an error on failure. If there is nothing for portage to do, then portage will exit with a message and a success condition. A resume list will persist until it has been completed in entirety or until another aborted merge list replaces it.

The resume history is capable of storing two merge lists. After one resume list completes, it is possible to invoke --resume once again in order to resume an older list.

Searches for matches of the supplied string in the portage tree. If you want to search the package descriptions as well, use the --searchdesc action. Matches the search string against the description field as well as the package name. Take caution as the descriptions are also matched as regular expressions. NOTE: The emerge-webrsync program will download the entire portage tree as a tarball, which is much faster than emerge --sync for first time syncs. Removes all matching packages.

This does no checking of dependencies, so it may remove packages necessary for the proper operation of your system. Its arguments can be atoms or ebuilds. For a dependency aware version of --unmerge , use --depclean or --prune. When displaying USE and other flag output, combines the enabled and disabled lists into one list and sorts the whole list alphabetically.

Before performing the action, display what will take place server info for --sync , --pretend output for merge, and so forth , then ask whether to proceed with the action or abort. Using --ask is more efficient than using --pretend and then executing the same command without --pretend , as dependencies will only need to be calculated once. Note that the input buffer is not cleared prior to the prompt, so an accidental press of the "Enter" key at any time prior to the prompt will be interpreted as a choice!

Use the --ask-enter-invalid option if you want a single "Enter" key press to be interpreted as invalid input. When used together with the --ask option, interpret a single "Enter" key press as invalid input.

This helps prevent accidental acceptance of the first choice. This option is intended to be set in the make. Automatically unmask packages and generate package. This option is enabled by default. If any configuration changes are required, then they will be displayed after the merge list and emerge will immediately abort.

If the displayed configuration changes are satisfactory, you should copy and paste them into the specified configuration file s , or enable the --autounmask-write option. USE and license changes always use the latter behavior. If --autounmask is enabled, no package. This leads to unsatisfied dependencies if no other solution exists. If the corresponding package. This way it is always ensured that the new changes take precedence over existing changes.

Specifies an integer number of times to backtrack if dependency calculation fails due to a conflict or an unsatisfied dependency default: Tells emerge to ignore binary packages if their use flags don't match the current configuration. Tells emerge to build binary packages for all ebuilds processed in addition to actually merging the packages. Useful for maintainers or if you administrate multiple Gentoo Linux systems build once, emerge tbz2s everywhere as well as disaster recovery.

An alternative for already-merged packages is to use quickpkg 1 which creates a tbz2 from the live filesystem. A space separated list of package atoms for which no binary packages should be built. This option overrides all possible ways to enable building of binary packages. Creates binary packages for all ebuilds processed without actually merging the packages. This comes with the caveat that all build-time dependencies must already be emerged on the system.

Tells emerge to include installed packages where USE flags have changed since installation. This option also implies the --selective option. Unlike --newuse , the --changed-use option does not trigger reinstallation when flags that the user has not enabled are added or removed. Use this in conjunction with the --pretend option. This will show the ChangeLog entries for all the packages that will be upgraded. Enable or disable color output.

Used alongside --pretend to cause the package name, new version, and old version to be displayed in an aligned format for easy cut-n-paste. This causes emerge to consider the deep dependencies of all packages from the world set. With this option enabled, emerge will bail out if it determines that the given operation will break any dependencies of the packages that have been added to the graph.

Like the --deep option, the --complete-graph option will significantly increase the time taken for dependency calculations. Note that, unlike the --deep option, the --complete-graph option does not cause any more packages to be updated than would have otherwise been updated with the option disabled. Trigger the --complete-graph behavior if an installed package version will change upgrade or downgrade.

Tells emerge to run the emerge command in --debug mode. In this mode the bash build environment will run with the -x option, causing it to output verbose debugging information to stdout. This also enables a plethora of other output mostly dependency resolution messages. This flag forces emerge to consider the entire dependency tree of packages, instead of checking only the immediate dependencies of the packages.

As an example, this catches updates in libraries that are not directly listed in the dependencies of a package. Also see --with-bdeps for behavior with respect to build time dependencies that are not strictly required. There are two types of upgrades, partial and full, or regular and deep.

The partial or regular will only update packages that have a direct update. Using the deep option will update the package and it's dependencies. If the system USE flags are changed then a check should be made to determine which packages need to be rebuilt. The utility equery provides information about the packages, use flags and other good stuffs. There are short options available, long options used for descriptive purposes.