Codice: Seleziona tutto
2009-04-18-java-config-wrapper-0.16
Title Generation 1 Java Setup Deprecated
Author Petteri Räty <betelgeuse@gentoo.org>
Posted 2009-04-18
Revision 2
For a long time the Java team required a 1.4 JDK to be
installed in order for old java ebuilds to work. All these
ebuilds are now gone from the main tree so the requirement
to have a 1.4 JDK installed has been lifted.
In order to remove things left over by the generation 1
setup please run java-check-environment and follow the
instructions.
If you want to remove 1.4 JDKs, you should use emerge --depclean.
Depending on what you have installed you might not need a
1.4 JDK any more. To see if you still need a 1.4 JDK use:
emerge -av --depclean virtual/jdk:1.4
If you don't need virtual/jdk:1.4 any more then you can remove the
individual JDKs. First get the list of installed JDKs with
eselect and then remove those that are not needed any longer with
depclean, for example:
eselect java-vm list
emerge -av --depclean sun-jdk:1.4
2011-08-28-mesa-r600g
Title Mesa r600 driver now defaults to gallium
Author Chí-Thanh Christopher Nguyễn <chithanh@gentoo.org>
Posted 2011-08-28
Revision 1
This news item is relevant to you only if you have a Radeon graphics
chipset and use the free/open source driver.
The r600 driver that provides 3D acceleration for Radeon HD 2400 and
later cards comes in the "classic" and "gallium" variants. The gallium
driver is based on the new Gallium3D infrastructure and was chosen as
the default driver for media-libs/mesa-7.11.
Existing users will not be switched automatically. To switch to the
r600 gallium driver, use the following command:
eselect mesa set r600 gallium
Gallium3D requires kernel modesetting (KMS). If your system is not yet
configured for KMS, consult the X Server Configuration HOWTO for
instructions prior to switching:
http://www.gentoo.org/doc/en/xorg-config.xml
Questi sono errori?:
Codice: Seleziona tutto
emerge --depclean
* Depclean may break link level dependencies. Thus, it is
* recommended to use a tool such as `revdep-rebuild` (from
* app-portage/gentoolkit) in order to detect such breakage.
*
* Always study the list of packages to be cleaned for any obvious
* mistakes. Packages that are part of the world set will always
* be kept. They can be manually added to this set with
* `emerge --noreplace <atom>`. Packages that are listed in
* package.provided (see portage(5)) will be removed by
* depclean, even if they are part of the world set.
*
* As a safety measure, depclean will not remove any packages
* unless *all* required dependencies have been resolved. As a
* consequence, it is often necessary to run `emerge --update
* --newuse --deep @world` prior to depclean.
Calculating dependencies... done!
* Dependencies could not be completely resolved due to
* the following required packages not being installed:
*
* >=dev-db/libdbi-drivers-0.8.3 pulled in by:
* dev-db/libdbi-0.8.3
*
* Have you forgotten to do a complete update prior to depclean? The
* most comprehensive command for this purpose is as follows:
*
* emerge --update --newuse --deep --with-bdeps=y @world
*
* Note that the --with-bdeps=y option is not required in many
* situations. Refer to the emerge manual page (run `man emerge`)
* for more information about --with-bdeps.
*
* Also, note that it may be necessary to manually uninstall
* packages that no longer exist in the portage tree, since it may
* not be possible to satisfy their dependencies.
