On Mon, 2005-01-17 at 20:24 +0200, Dan Armak wrote: > But it's an interesting problem. If the portage side provided eg readonly > access to an unpacked kde source tree, the ebuilds could build everything > out-of-tree. Or we could create a tree of hardlinks and build inside that, > since we don't have write access to those hardlinks. (This speedup would > apply to the monolithic ebuilds, too.) > > I'd be willing to try implementing it if I was convinced that the unpacking > was the main overhead introduced by increasing the amount of ebuilds. Right > now the main overhead is running configure multiple times (how long does that > take you?), so I want to see confcache get here first, and meanwhile work on > other speedups like unsermake, and when all that's done I'll try out this > idea.
The kde stuff could DEPEND on some package that's merely the unpacked source. If you have builddir != srcdir, you could install the src to /usr/src or wherever else, then build in TMPDIR. Since it's only a DEPEND, it could be depcleaned at a later time, or just uninstalled. It may not be the most elegant conceivable solution, but it sounds as if it would work. -- [email protected] mailing list
