On Sun, May 08, 2005 at 12:47:05AM +0900, Jason Stubbs wrote: > 6 Portage must disallow the creation of binary packages where all > dependencies are not in the same PREFIX. First level, second level... ? I'd rather see the deps/prefix data slapped into the binpkg, and tracked alongside, and verified prior to installation. Reason being- say a package links against libssl, and is built to be installed into a user's directory (irssi for example). A restriction of the sort you're specifying would block irssi from ever being binpkg'd for home installation.
> I was planning to summarize home install support here, Clarify please :) Offhand, I don't see why a bin repo for a home target isn't viable, along with a vdb repo in the same location. It's a bit trickier, but I suspect it might be a bit more flexible in the long run. ~brian -- [email protected] mailing list
