Sebastian Redl <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Thu, 19 Oct 2006 21:31:52 +0200:
> Vladimir G. Ivanovic wrote: > >>Is what I'm after possible? >> >> > AFAIK not through Portage. You could, however, go to the work directory > and issue the commands of the ebuild yourself, then create a ".compiled" > file in the right directory (parent directory of "work", I think), and > finish with "ebuild install qmerge". > > Of course, that voids the warranty ;) It also screws things up a bit for portage as there's a couple things it does beyond the ebuild at the end of the compile stage, that become holes in portage's records later on if you simply issue the ebuild compile commands and create the .compiled file manually. I found this out the hard way. =8^( I forgot the details now, but I did have a (now outdated) portage patch available that allowed a workaround. After I got the memory stability issue fixed that was causing my crashes, and I could reliably complete merges, I didn't find it so necessary to maintain the patch any more. I could dust it off and brush up on the forgotten details (updating them as necessary for newer portage), if it would be useful. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [email protected] mailing list
