Differences between version 16 and revision by previous author of GentooNotes.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 16 | Last edited on Tuesday, June 21, 2005 4:30:45 pm | by DanielLawson | Revert |
| Older page: | version 15 | Last edited on Tuesday, June 21, 2005 2:58:57 pm | by JohnMcPherson | Revert |
@@ -62,15 +62,11 @@
This will only rebuild packages whose <tt>USE</tt> flags would change
!!! An <tt>emerge</tt> clobbered something vital, but I didn't see what!
-This happens a lot. If you run <tt>emerge -Du world</tt>, and don't have a tediously slow machine, chances are pretty good that at some point you'll emerge a package which will "automatically" overwrite some config option. It'll tell you about it, but you probably won't be watching. The <tt>shadow<
/tt> package was doing this
for a while
, and was overwriting
the [PAM] configuration -- screwing anyone who used any non-standard [PAM] options
.
+This happens a lot. If you run <tt>emerge -Du world</tt>, and don't have a tediously slow machine, chances are pretty good that at some point you'll emerge a package which will "automatically" overwrite some config option. It'll tell you about it, but you probably won't be watching. There is a [bug filed against portage | http:
//bugs.gentoo.org/show_bug.cgi?id=11359]
for this
, but it's been about two years
and a half and nothing has actually happened. It's possible this will be included in
the 'next version of portage', whenever that comes out
.
-* Don't emerge lots of packages at once. And make sure you read
the output. This isn't overly useful advice.
-* Set
the <tt>PORT_LOGDIR</tt> variable in <tt>/etc/make.conf</tt>, and read over the log files generated by each <tt>emerge</tt> process. Or better yet, grab
[portlog-info
|http://tdegreni
.free.fr/
gentoo/portlog-info] to parse the output and give you the bits you want
.
-* Grab [ehush | http://abeni.sf.net
/ebuilds
/ehush
] and use it to emerge instead -- it suppresses the noise and only shows useful information / warning content
.
-
-The last two options are ok, however this should be part of
portage, not an external script. There is
a [bug filed against portage | http://bugs
.gentoo.org
/show_bug.cgi?id=11359] for this, but it's been about two years and nothing has actually happened. It's possible this will be included in the 'next version of portage', whenever that comes out
.
+By far
the best recommendation is to grab
the very excellend
[enotice
| http://dev
.gentoo.org
/~eldad
/] script
. This modifies
portage slightly
, and saves any ewarn or einfo output to
a specific logdir
. You can then run <tt>enotice<
/tt> to browse them
.
!!! <tt>USE</tt> flags for specific packages
You can set specific <tt>USE</tt> flags for a given package in the package attribute <tt>/etc/portage/package.use</tt>. Those flags will then be applied to that package as though they were specified on the CommandLine. Eg., to build BitTorrent without [X11] support:
