emerge -1 --usepkg --pretend --verbose pkg_spec_from_equery
then the change in USE-Flags are showen and my _correct_ binarys are used.
There's probably a good reason for it being the way it is, but it
doesn't sound as transparent as we might like.
yes may be... if so, I would like to know the reason :-)
A further interesting scenario might be to have a binary package
available built with different USE flags to those on the target machine,
and seeing if it gets installed or not. I guess it shouldn't. But then
there's the CFLAGS issue as well, and I'm even more unsure how that's
supposed to be handled.
If you build a binary with different USE flags then on the target it
would be merged as ebuild and not as binary. But this seems only to work
with --usepkg not with --getbinpkg. ?? CFLAGS handling is done in the same
way like USE flags. You can use the tbz2tool to split your binary into
data (tar) and info (text). In this info-text is every thing stored like
USe, CFALGS, ....
I'm still pretty new to Gentoo, but is this perhaps related to the
feature I've read about (and maybe misremembered) regarding only
packages that you explicity emerge going into world (dependencies
don't)? I wonder if you'd see different results if you explicitly
emerged cups rather than it having been implicity emerged due to a
dependency. By doing the emerge you described you've 'promoted' those
packages from implicit to explicit emerge.
Hm... yes every time you type emege .... it will be recorded in the
world-file, expect emerge --oneshot (-1)... so my explicit merge will not
be recorded in world it stays what it was before (world or dependency).
So I understand --usepkg in this way to use binary if all USE/C flags etc
match. If not fallback to ebuilds. So I know I have the right binary pkgs,
why does:
emerge -uDpv --newuse world
and
emerge -uDpv --newuse --usepkg world
show different results?
Sascha.
--
gentoo-user@gentoo.org mailing list
