> > cludging DEPEND manually or with tools break the whole idea of making > > packages from the same stuff we make source builds with. > > It's not really a kludge. The RDEPEND line specifies what versions of > what packages the about-to-be-installed package needs - it's just that > binary packages are stricter in their version needs that source > packages. Since we're making sure that the compiled ebuilds are > tightly coupled to the compiled source, there's no way for them to cause > damage.
Well, if you put a dummy ebuild to satisfy a binary ebuild package in the overlay dir... well, it's a kludge. A better way to do it would be to place the RDEPEND information in the .tbz2 , and on a binary emerge have portage checkout if the RDEPEND for this package is satisfied. BTW, same for useflags. If I emerge a binary package portage doesn't care about the use flags the binary was build with - just the flags I specify, that's broken behaviour imho, and you have to manually correlate the useflags to prevent breakage. Eldad -- [EMAIL PROTECTED] mailing list
