Since I'm on a slowish system, I'm thinking of building and using binary packges through emerge. However, I'd like to know what, if any, meta-information is in the packages.
For any out there that are unclear, I'm not talking about binary (*-bin) ebuilds, I'm refering to binary packages created through quickpkg, emerge -b, or emerge -B. Do these packages remember what CHOST they were built for? So, if I change my CHOST or move the packages to a different machine, will emerge ignore the packages that are not relevant? Do these packages remember what version of libc or gcc they were built with, if it is relevant? [Perl and Python packages would probably not need this information; ditto with Java packages compiled into bytecode (e.g. with javac) and not natively (e.g. with gcj).] Again, this would be so that emerge would ignore package that wouldn't work on the current system (if the system changed or packages were moved). Do these packages remember what relevant use flags were set? Even though they aren't a volitile as when I was first using gentoo, I do still tweak my use flags. If I change them I wouldn't want to use a package that was affected by the change. Is there relevant documentation on this? I know 'man portage' and 'man emerge' fairly well, but they are a bit vague when it comes to binary packages. I'll gladly RTFM if I knew a good one. I just don't want to have to RTFSource. -- Boyd Stephen Smith Jr. [EMAIL PROTECTED] ICQ: 514984 YM/AIM: DaTwinkDaddy -- gentoo-user@gentoo.org mailing list
