New in pkgcore:

--ignore-failures:

Ignore resolution/build failures, skipping to the next step. Think of it as the equivalent of --skipfirst, just without the commandline interruption.

It goes without saying that this feature should be used with care. It is primarily useful for a long chain of non-critical updates, where a failure is not an issue.

A good example of usage is if you want to build mozilla-firefox and openoffice overnight: both take a long while to build (including their dependencies), and the user is after getting as many packages built for the targets as possible, rather then having the 5th build out of 80 bail out without even attempting the other 75.

Long term, this feature will likely be replaced with a more finely tuned option.

--preload-vdb-state:

This preloads the installed packages database, causing the resolver to work with a complete graph, disallowing actions that conflict with installed packages. If it's disabled, it's possible for the requested action to conflict with already installed dependencies that aren't involved in the graph of the requested operation.

Moved, in pmerge:

--depclean:

--clean

--with-bdeps:

--with-built-depends

Moved out of pmerge:

--regen:

See regen

No equivalents:

--info:

pconfig is the closest equivalent at the moment; it's rather verbose.

--config:

This may be implemented in pmaint in the future, possibly 0.4.x.

--prune:

Currently not implemented; Portage's implementation of it ignores slots, trying to force a max version for each package. This is problematic since it can remove needed slotted packages that are of a lesser version.

Any package that requires slotting (automake for example) generally will be screwed up by emerge --prune's behaviour.

The long term intention is to implement this functionality safely. Effectively, to try to minimize the resolved dependency graph to the minimal number of packages involved.

--resume, --skipfirst:

Not yet implemented.

--metadata:

Not implemented: pkgcore doesn't need cache localization.

If the user is after copying cache data around, pclone_cache can be used.

--fetch-all-uri:

Not yet implemented.

--buildpkg:

Not yet implemented.

--getbinpkg, --getbinpkgonly:

Remote Binhost v1 support will not be implemented in pkgcore, instead favoring the genpkgindex approach Ned Ludd (solar) has created.

There are two main reasons for not implementing this:

• The design of v1 allows for collisions in the package namespace; category is ignored. Furthermore, this collision isn't easily detectable; pulling mysql-5.0 from the server may get you virtual/mysql-5.0 or dev-db/mysql-5.0

• The design is god awfully slow. To get the metadata for a binpkg from an HTTP server, it requires (roughly) a HEAD request (tbz2 length), a ranged GET request to grab the last 16 bytes for the XPAK segment start, and another ranged request to pull the metadata.

  That's per package. You can cache, but the roundtrips add up quickly.

The main reason why v1 support will not be added to pkgcore is the package namespace collision issue; as both of these issues will be addressed in v2 pkgcore will go this route.

--tree:

This is formatter-dependent; it may be included in 0.4.

--verbose:

Not yet implemented.

--alphabetical, --columns:

These won't be implemented in pkgcore.

--changelog:

At some point will be accessible via pquery.