On Sunday 29 May 2005 04:38 pm, Mark Shields <[EMAIL PROTECTED]> top-posted, and I had to fix it: > On 5/29/05, Boyd Stephen Smith Jr. <[EMAIL PROTECTED]> wrote: > > 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. > > > > 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. > > http://www.gentoo.org/doc/en/handbook/handbook-hppa.xml?part=2&chap=3
Not much there, really. I know the options to pass to emerge, FEATURES to use, directories packages are built into / used from, and various environment variables for fetching remote binary packages. I want to know more about the structure of portage binary packages and how portage uses the information (if any) in the package > By definition, prebuilt packages are compiled binaries (if there ever > were a redundant phrase...). Compiled programs use the CHOST they're > compiled with. Yes, yes. I understand that the packages were compiled with a certain CHOST, libraries, compiler, and USE flags and when installed will use those options. I want to know what, if any, information about the package's build environment is stored in the package binary and what, if any, of the information is used by portage/emerge to decide when to use a binary package. I've got a suspision that emerge/portage just matches based on package name/version, this makes binary packaging much less useful, IMHO. -- Boyd Stephen Smith Jr. [EMAIL PROTECTED] ICQ: 514984 YM/AIM: DaTwinkDaddy -- gentoo-user@gentoo.org mailing list
