1 |
> can we full upgrade |
2 |
> the system, or are we stuck, as with every linux, with the stock |
3 |
> binary install ? I mean, instead of a "make buildworld", can we |
4 |
> upgrade the "world" package, from src ? |
5 |
> |
6 |
|
7 |
to update the system in gentoo we do: |
8 |
|
9 |
# emerge --update world |
10 |
|
11 |
which will download, compile and install any outdated package (except |
12 |
for those that you pinned or are not part of the world "profile") |
13 |
|
14 |
here is the output of # emerge --help, which should give you an idea of |
15 |
how it works: |
16 |
bangert@kniffel bangert $ emerge --help |
17 |
|
18 |
Usage: emerge [ options ] [ action ] [ ebuildfile | tbz2file | |
19 |
dependency ] ... |
20 |
emerge [ options ] [ action ] system |
21 |
emerge [ --clean -c ] sync | rsync |
22 |
emerge --help -h [ rsync | system | config ] |
23 |
|
24 |
Help (this screen): |
25 |
--help (-h short option) |
26 |
Displays this help; an additional argument (see above) |
27 |
will tell |
28 |
emerge to display detailed help. |
29 |
|
30 |
Actions: |
31 |
clean (-c short option) |
32 |
Cleans the system by removing outdated packages which will |
33 |
not |
34 |
remove functionalities or prevent your system from |
35 |
working. |
36 |
The arguments can be in several different formats : |
37 |
* world |
38 |
* system |
39 |
* /var/db/pkg/category/package-version, or |
40 |
* 'dependency specification' (in single quotes is best.) |
41 |
Here are a few examples of the dependency specification |
42 |
format: |
43 |
binutils matches |
44 |
binutils-2.11.90.0.7 and binutils-2.11.92.0.12.3-r1 |
45 |
>binutils-2.11.90.0.7 matches |
46 |
binutils-2.11.92.0.12.3-r1 |
47 |
sys-devel/binutils matches |
48 |
binutils-2.11.90.0.7 and binutils-2.11.92.0.12.3-r1 |
49 |
sys-devel/binutils-2.11.90.0.7 matches |
50 |
binutils-2.11.90.0.7 |
51 |
>sys-devel/binutils-2.11.90.0.7 matches |
52 |
binutils-2.11.92.0.12.3-r1 |
53 |
>=sys-devel/binutils-2.11.90.0.7 matches |
54 |
binutils-2.11.90.0.7 and binutils-2.11.92.0.12.3-r1 |
55 |
<sys-devel/binutils-2.11.92.0.12.3-r1 matches |
56 |
binutils-2.11.90.0.7 |
57 |
<=sys-devel/binutils-2.11.92.0.12.3-r1 matches |
58 |
binutils-2.11.90.0.7 and binutils-2.11.92.0.12.3-r1 |
59 |
|
60 |
unmerge (-C short option) |
61 |
WARNING: This action can remove important packages! |
62 |
Removes all matching packages without checking for |
63 |
outdated. |
64 |
versions. This thus effectively removes a package |
65 |
completely from |
66 |
your system. Specify arguments using the dependency |
67 |
specification |
68 |
format described in the clean action above. |
69 |
|
70 |
prune (-P short option) |
71 |
WARNING: This action can remove important packages! |
72 |
Removes all older versions of a package from your system. |
73 |
This action doesn't always verify the possible binary |
74 |
incompatibility between versions and can thus remove |
75 |
essential |
76 |
dependencies from your system. |
77 |
The argument format is the same as for the clean action. |
78 |
|
79 |
search (-s short option) |
80 |
searches for matches of the supplied string in the current |
81 |
local |
82 |
portage tree. The search string is a regular expression. |
83 |
A few examples: |
84 |
emerge search '^kde' |
85 |
list all packages starting with kde |
86 |
emerge search 'gcc$' |
87 |
list all packages ending with gcc |
88 |
emerge search '' or |
89 |
emerge search '.*' |
90 |
list all available packages |
91 |
|
92 |
inject (-i short option) |
93 |
Add a stub entry for a package so that Portage thinks that |
94 |
it's |
95 |
installed when it really isn't. Handy if you roll your |
96 |
own |
97 |
packages. Example: |
98 |
emerge inject gentoo-sources-2.4.19 |
99 |
|
100 |
Options: |
101 |
--autoclean (-a short option) |
102 |
emerge normally cleans out the package-specific temporary |
103 |
build directory before it starts the building a package. |
104 |
With |
105 |
--autoclean, it will also clean the directory *after* the |
106 |
build completes. This option is automatically enabled for |
107 |
normal users, but maintainers can use this option to |
108 |
enable |
109 |
autocleaning. |
110 |
|
111 |
--buildpkg (-b short option) |
112 |
tell emerge to build binary packages for all ebuilds |
113 |
processed |
114 |
(in addition to actually merging the packages. Useful for |
115 |
maintainers or if you administrate multiple Gentoo Linux |
116 |
systems (build once, emerge tbz2s everywhere). |
117 |
|
118 |
--debug (-d short option) |
119 |
Tell emerge to run the ebuild command in --debug mode. In |
120 |
this |
121 |
mode, the bash build environment will run with the -x |
122 |
option, |
123 |
causing it to output verbose debug information print to |
124 |
stdout. |
125 |
--debug is great for finding bash syntax errors. |
126 |
|
127 |
--emptytree (-e short option) |
128 |
Virtually tweaks the tree of installed packages to only |
129 |
contain |
130 |
glibc, this is great to use together with --pretend. This |
131 |
makes |
132 |
it possible for developers to get a complete overview of |
133 |
the |
134 |
complete dependency tree of a certain package. |
135 |
|
136 |
--fetchonly (-f short option) |
137 |
Instead of doing any package building, just perform |
138 |
fetches for |
139 |
all packages (main package as well as all dependencies.) |
140 |
|
141 |
--nodeps |
142 |
Merge specified packages, but don't merge any |
143 |
dependencies. |
144 |
Note that the build may fail if deps aren't satisfied. |
145 |
|
146 |
--noreplace (-n short option) |
147 |
Skip the packages specified on the command-line that have |
148 |
already been installed. Without this option, any |
149 |
packages, |
150 |
ebuilds, or deps you specify on on the command-line *will* |
151 |
cause |
152 |
Portage to remerge the package, even if it is already |
153 |
installed. |
154 |
Note that Portage won't remerge dependencies by default. |
155 |
|
156 |
--oneshot |
157 |
Emerge as normal, but don't add packages to the world |
158 |
profile for |
159 |
later updating. |
160 |
|
161 |
|
162 |
--onlydeps (-o short option) |
163 |
Only merge (or pretend to merge) the dependencies of the |
164 |
specified packages, not the packages themselves. |
165 |
|
166 |
--pretend (-p short option) |
167 |
instead of actually performing the merge, simply display |
168 |
what |
169 |
ebuilds and tbz2s *would* have been installed if --pretend |
170 |
weren't used. Using --pretend is strongly recommended |
171 |
before |
172 |
installing an unfamiliar package. In the printout, N = |
173 |
new, |
174 |
U = upgrading, R = replacing, B = blocked by an already |
175 |
installed |
176 |
package. |
177 |
|
178 |
--update (-u short option) |
179 |
Updates packages to the most recent version available. |
180 |
|
181 |
--usepkg (-k short option) |
182 |
tell emerge to use binary packages (from $PKGDIR) if they |
183 |
are |
184 |
available, thus possibly avoiding some time-consuming |
185 |
compiles. |
186 |
This option is useful for CD installs; you can export |
187 |
PKGDIR=/mnt/cdrom/packages and then use this option to |
188 |
have |
189 |
emerge "pull" binary packages from the CD in order to |
190 |
satisfy |
191 |
dependencies. |
192 |
|
193 |
--verbose (-v short option) |
194 |
Tell emerge to run in verbose mode. Currently, this |
195 |
causes |
196 |
emerge to print out GNU info errors, if any. |
197 |
|
198 |
(urghs - not really... sorry) |
199 |
|
200 |
> This is a must for me, as I mainly work from home, and I'd hate to go |
201 |
> some place just to upgrade a server via cd or anything similar. |
202 |
> |
203 |
> Congrats on an interesting linux :-] |
204 |
|
205 |
-- |
206 |
regards | Please file bugreports here: |
207 |
Thilo | http://bugs.gentoo.org |