Re: [PATCH] Set up argv0_path correctly, even when argv[0] is just the basename
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 26, 2008, 17:31 UTC
- Message-ID
- <7vod4kft7d.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <alpine.DEB.1.00.0807261613120.26810@eeepc-johanness>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> When the program 'git' is in the PATH, the argv[0] is set to the basename.
While it may be true, I do not think it matters that we cannot get the full path _UNLESS_ we are doing the relative "../" business.
> However, argv0_path needs the full path, so add a function to discover the > program by traversing the PATH manually.
I think unconditionally requiring argv0_path to be set is the root cause of the bug. Unless we do not fix _that_, we will have to make a needless call to lookup_program_in_path() even when nobody needs that information, which is unacceptable.