Differences between version 8 and previous revision of GentooNotes.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 8 | Last edited on Tuesday, November 2, 2004 8:57:59 am | by DanielLawson | Revert |
| Older page: | version 2 | Last edited on Tuesday, June 17, 2003 3:08:09 pm | by CraigBox | Revert |
@@ -1,22 +1,37 @@
-!Notes on GentooLinux
+!!! Sundry helpful trivia
-See InstallingGentoo
+* 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]
-!About Masked packages
+!!! An <tt>emerge</tt> clobbered something vital, but I didn't see what!
-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
/usr/portage/profiles/packages.mask
, 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)
+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.
-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
.
+* 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.
-!Installing Masked
packages
+!!! <tt>USE</tt> flags for specific
packages
-You can either install
the file using an explicit ebuild, eg:
- emerge
/usr
/portage/wm-x11/xfce4
/xfce4-3
.90
.ebuild
+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:
-This will work
for all types
of masking
, however it only works for that one ebuild
. You'll find that XFCE 4 depends on a metric assload of other
packages, and so
you have to manually walk its dependancy tree
, installing each one
by hand
. XFCE 4
is in the 'unstable' branch, and we can tell emerge to allow packages in this branch by setting
the 'ACCEPT_KEYWORDS
' environment variable to "~x86"
+<verbatim>
+echo net-p2p/bittorrent -X >> /etc/portage/package.use
+</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)
+
+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.
-For example:
-
ACCEPT_KEYWORDS="~x86"
emerge xfce4
+The only recommended way to install masked packages is to add to <tt>/etc/portage/packages.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:
-Will happily build XFCE
4 (actually 3
.9
.something, its
the 4 beta release) and all its depedencies
.
+<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
+</verbatim>
