On 24/12/2013 12:59, Konstantinos Agouros wrote:
> Hi,
>
> I have several machines of the same architecture so I build using distcc
> and --buildpkg and then try to emerge -uk on the other boxes. However
> there are differences in useflags so I understand, that in some cases
> on the 2nd or 3rd box the package has to be rebuilt. What I still don't get
> is: How can I recognize _why_ a package is not merged from the binary.
> emerge -uDkvp --binpkg-respect-use y shows the use flags in colors but
> I don't know how to read this.
If portage will use the binpkg, the line is printed in a pink/purple color.
If it can't use the binpkg, it uses the normal colours (green here).
I always get a report if USE differs, what is your setting of
--binpkg-respect-use? The usual report looks like this:
# USE="vanilla" emerge -pvk bash
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] app-shells/bash-4.2_p45 USE="examples net nls plugins
(readline) vanilla* -afs -bashlogger -mem-scramble" 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB
!!! The following binary packages have been ignored due to non matching USE:
=app-shells/bash-4.2_p45 -vanilla
NOTE: The --binpkg-respect-use=n option will prevent emerge
from ignoring these binary packages if possible.
Using --binpkg-respect-use=y will silence this warning.
>
> Also: Are packages with the bindist useflag are automatically exempt from
> being binary merged if -bindist is given?
No.
binpkgs and bindist are two completely different things and not related
in any way
--
Alan McKinnon
alan.mckin...@gmail.com
