Differences between version 13 and revision by previous author of GentooNotes.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 13 | Last edited on Friday, April 8, 2005 10:29:14 am | by NickJohnson | Revert |
| Older page: | version 12 | Last edited on Saturday, March 19, 2005 2:40:53 pm | by DanielLawson | Revert |
@@ -69,9 +69,9 @@
</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:
