77cb17e940
The git suite may not be in PATH (and thus programs such as git-send-pack could not exec git-rev-list). Thus there is a need for logic that will locate these programs. Modifying PATH is not desirable as it result in behavior differing from the user's intentions, as we may end up prepending "/usr/bin" to PATH. - git C programs will use exec*_git_cmd() APIs to exec sub-commands. - exec*_git_cmd() will execute a git program by searching for it in the following directories: 1. --exec-path (as used by "git") 2. The GIT_EXEC_PATH environment variable. 3. $(gitexecdir) as set in Makefile (default value $(bindir)). - git wrapper will modify PATH as before to enable shell scripts to invoke "git-foo" commands. Ideally, shell scripts should use the git wrapper to become independent of PATH, and then modifying PATH will not be necessary. [jc: with minor updates after a brief review.] Signed-off-by: Michal Ostrowski <mostrows@watson.ibm.com> Signed-off-by: Junio C Hamano <junkio@cox.net>
21 lines
511 B
C
21 lines
511 B
C
#ifndef RUN_COMMAND_H
|
|
#define RUN_COMMAND_H
|
|
|
|
#define MAX_RUN_COMMAND_ARGS 256
|
|
enum {
|
|
ERR_RUN_COMMAND_FORK = 10000,
|
|
ERR_RUN_COMMAND_EXEC,
|
|
ERR_RUN_COMMAND_WAITPID,
|
|
ERR_RUN_COMMAND_WAITPID_WRONG_PID,
|
|
ERR_RUN_COMMAND_WAITPID_SIGNAL,
|
|
ERR_RUN_COMMAND_WAITPID_NOEXIT,
|
|
};
|
|
|
|
#define RUN_COMMAND_NO_STDIO 1
|
|
#define RUN_GIT_CMD 2 /*If this is to be git sub-command */
|
|
int run_command_v_opt(int argc, char **argv, int opt);
|
|
int run_command_v(int argc, char **argv);
|
|
int run_command(const char *cmd, ...);
|
|
|
|
#endif
|