[gentoo-portage-dev] Re: running ebuild in src tree

[Duncan]

Joakim Tjernlund posted on Fri, 13 Mar 2015 08:13:01 +0000 as excerpted:

> When you are developing SW you do the edit/build cycle often and it is
> really annoying to copy a big src tree, rebuild everything (as
> timestamps, deps changes), move to another src to do any debugging etc.
> Try it on your own development by just copying you src tree every time
> you want to build, you get very tired of it real soon :)

That's what ccache is for. For some time I was following live-kde (tho 
I'm not ATM as kf5 wasn't working for me yet, last I tried, and kde4 
development is pretty much dead, now) and doing rebuilds several times a 
week, so I know what it's like. =:^)

But I do get your point, now.

Still, unless it's something like firefox, while I used to get irritated 
with the extra build time back when I was running a dual-core, a quad-
core improved that, and with my current 6-core bulldozer-1 (fx6100), 
PORTAGE_TMPDIR on tmpfs, and the system and ccache on ssd, most of the 
time I just let it do the rebuild.  It's really not worth the trouble 
worrying about it any more, particularly when I can be doing other stuff 
while it builds.

But you're right, being able to build right in an existing git clone 
without the hassle of hacks such as you posted, and even configuring live-
ebuilds to do just that with say a variable setting that could be set by 
a package.env pointer, would be nice indeed.  Local hacking on such live-
build packages would be quite a bit easier, that way.

-- 
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