blob: ff22f971f84040672149ebe522bec37631e9c9ea (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
|
======
pmerge
======
.. include:: pmerge/main_synopsis.rst
.. include:: pmerge/main_description.rst
Portage Compatibility
=====================
With regards to portage compatibility, pmerge provides much of the same
functionality that emerge does. In general, it should be possible to use
both pmerge and emerge on the same system in a sane fashion. For example,
pmerge can be used to install packages and then emerge should be able to
upgrade or uninstall them, or vice versa. Also, binary packages created using
pmerge should be able to be installed properly using emerge. Any major
compatibility issue that arises when trying to use both package managers is
probably a bug and should be reported.
In terms of option naming, pmerge tries to remain somewhat compatible to
portage so running ``pmerge -1av`` should work the same as ``emerge -1av`` when
using portage. However, pmerge doesn't implement nearly the same amount of
options that portage provides so many of the more obscure ones are missing. In
addition, pmerge defaults to a portage compatible output format that closely
matches the default colors and output structure that portage uses.
.. include:: pmerge/main_options.rst
Example Usage
=============
Merge pkgcore from the gentoo repo::
pmerge sys-apps/pkgcore::gentoo
Output a simple list of package atoms that would be updated for a global
update::
pmerge -uDp --formatter basic @world
Force new binpkgs to be built for the entire system set using a custom
configuration directory::
pmerge -uDSeb --config /home/foo/portage @system
See Also
========
emerge(1), pmaint(1), pebuild(1), pquery(1)
|
GitWeb
