Thank you, Yixun.
On 2023-08-11 02:23, Yixun Lan wrote:
> understanding git bisect should be enough to keep you going..
Yes, I actually just ended up doing what git bisect does but manually for now.
>> 2) Can I tell emerge not to clean the build directory between bisects so it
>> only recompiles the source files that actually changes between commits?
> it would be great to have this feature, but I don't know..
> or I'd not personally bother to go this way
My old machine takes 50 minutes to compile wine so it would've been great.
Guess it's time for me to upgrade. ;)
> EGIT_OVERRIDE_COMMIT_WINE_WINE? have you checked the emerge log? it's obvious
I noticed that by chance when I was looking in the log to check whether it
accepted the commit hash I fed it or not. But I ended up just using the
deprecated EGIT_COMMIT for this bisect and running it manually. Since most of
the time is spent compiling it wasn't that much work but I'll be sure to try a
more automated method next time now that I got the last pieces of the puzzle. :)
Just out of curiosity, what decides what the suffix to those EGIT_OVERRIDE_
variables will become? I was unable to find any info of those in the Gentoo
Development Guide, although I only looked at the description of the
git-r3.eclass and that might have been the wrong place.
Regards
Morgan