Differences between version 16 and predecessor to the previous major change of GentooNotes.
Other diffs: Previous Revision, Previous Author, 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 12 | Last edited on Saturday, March 19, 2005 2:40:53 pm | by DanielLawson | Revert |
@@ -2,8 +2,19 @@
* To be able to su(1), you must be in group <tt>wheel</tt>: <tt>usermod -G wheel user</tt>
* To be able to use the SoundCard, you must be in group <tt>audio</tt>: <tt>usermod -G audio user</tt>
* There is a thread in the Gentoo about [Non-standard Portage Utilities | http://forums.gentoo.org/viewtopic.php?t=67849]
+
+!!!Package querying basics
+!Searching available package names
+ emerge search ''part of packagename''
+
+!Listing files in a package
+(old way)
+ qpkg -l ''packagename''
+(newer way)
+ equery f ''packagename''
+
!!! Changing <tt>USE</tt> flags
If you've added (or removed) some <tt>USE</tt> flags on your system, there will be some inconsistencies with how some packages are compiled.
@@ -51,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.
-
-* 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
.
+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
.
-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:
@@ -69,21 +76,21 @@
</verbatim>
!!! Masked Packages
-Packages can be flagged as masked for a number of reasons. Mostly they are masked because they might break something, or they WILL break something. These tend to be masked in <tt>/usr/portage/profiles/packages.mask</tt>, and you can either forcibly install the package (see later), or unmask the package by commenting out the line. Note that this file is rebuilt everytime you emerge sync. There is rumour of support for
a packages.unmask file, but this doesn't seem
to work (16 Jun 2003)
+Packages can be flagged as masked for a number of reasons. Mostly they are masked because they might break something, or they WILL break something. These tend to be masked in <tt>/usr/portage/profiles/packages.mask</tt>, and you can either forcibly install the package (see later), or unmask the package by commenting out the line. Note that this file is rebuilt everytime you emerge sync. There is a packages.unmask file, which allows you to unmask packages that have been explicitly masked
, but use
this with care: The package was probably masked for a good reason. You can look in /usr/portage/profiles/package.mask
to see what packages are masked and why, and copy the declaration to /etc/portage/packages.unmask to unmask it.
The other reason packages can be masked is that they are in the 'unstable' branch of the gentoo tree. This is essentially the same as unstable in debian. Sometimes things will break, othertimes they'll be fine. You're on your own.
The only recommended way to install masked packages is to add to <tt>/etc/portage/package.keywords</tt> an entry for the package you want to build. Do __not__, whatever you do, emerge the <tt>.ebuild</tt> directly, or try to override <tt>ACCEPT_KEYWORDS</tt> on the CommandLine. Eg., if you want to emerge [XFce]4 from the unstable tree, do:
<verbatim>
-echo wm-x11/xfce4 ~x86 >> /etc/portage/package.keywords
-echo =wm-x11/xfce4-4..0 ~x86 >> /etc/portage/package.keywords # specific version of the package
-echo ~wm-x11/xfce4-4..0 ~x86 >> /etc/portage/package.keywords # all revisions of a specific version
+echo '
wm-x11/xfce4 ~x86'
>> /etc/portage/package.keywords
+echo '
=wm-x11/xfce4-4..0 ~x86'
>> /etc/portage/package.keywords # specific version of the package
+echo '
~wm-x11/xfce4-4..0 ~x86'
>> /etc/portage/package.keywords # all revisions of a specific version
</verbatim>
!!! Useful utilities
* revdep-rebuild - checks for broken library dependancies and rebuilds
* equery - various queries you can do against the portage system, such as checking <tt>USE</tt> flag settings, dependancies and so on.
* enotice - this little tool keeps track of important information and notices (einfo / ewarn) from ebuilds, and logs them away for you to inspect. Very useful for boxes that have a large number of updates, where important bits (like, "we're overwriting your PAM config, fix it up afterwards" might get lost). http://dev.gentoo.org/~eldad/
