There are architecture-specific keywords for each package that let portage know which systems are compatible with the package. See portage 5 for more information. Note the equal sign.
I have mysql 4. All times are GMT. Re-running the emerge command with --autounmask-write automatically queues the required text file alteration :. As with all configuration files, the final update is made by running dispatch-conf or alternatively etc-update :. Examine the diff output of the configuration files, press q to exit the pager if no commands appear at the end , and then u for use-new to accept the alterations.
Press z to zap disregard the changes. The problem happens when the masked package that you just unmasked depends on other packages that are also masked.
You will then need to rinse and repeat the process to ensure that everything is in place so that you can install that unmasked package. The original poster did not specify which type of mask, and seems sufficiently ill-informed about masking that I am going to assume he or she may not know the consequences of overriding a mask. If the reader does know the consequences and just did not know the method, then ignore the rest of this post. Packages are masked on purpose, usually because they are not deemed suitable for consumption by unwarned users.
Unmasking the package is notification to Portage that you have been warned of the consequences of using the package, and want to proceed anyway. If a package is masked by keywords, that is an indication it may not or will not build and run correctly on your system. For instance, packages which are not bit clean are marked as broken on bit architectures.
A package which is "unstable" may work perfectly well or it may not. If the package is masked by package. Common reasons for placing a package in package.
0コメント