2008-05-20 10:48:54 +04:00
|
|
|
#include "cache.h"
|
2012-10-28 20:16:24 +04:00
|
|
|
#include "string-list.h"
|
2008-05-20 10:48:54 +04:00
|
|
|
|
2012-10-28 20:16:25 +04:00
|
|
|
/*
|
|
|
|
* A "string_list_each_func_t" function that normalizes an entry from
|
|
|
|
* GIT_CEILING_DIRECTORIES. If the path is unusable for some reason,
|
|
|
|
* die with an explanation.
|
|
|
|
*/
|
|
|
|
static int normalize_ceiling_entry(struct string_list_item *item, void *unused)
|
|
|
|
{
|
|
|
|
const char *ceil = item->string;
|
|
|
|
int len = strlen(ceil);
|
|
|
|
char buf[PATH_MAX+1];
|
|
|
|
|
|
|
|
if (len == 0)
|
|
|
|
die("Empty path is not supported");
|
|
|
|
if (len > PATH_MAX)
|
|
|
|
die("Path \"%s\" is too long", ceil);
|
|
|
|
if (!is_absolute_path(ceil))
|
|
|
|
die("Path \"%s\" is not absolute", ceil);
|
|
|
|
if (normalize_path_copy(buf, ceil) < 0)
|
|
|
|
die("Path \"%s\" could not be normalized", ceil);
|
|
|
|
len = strlen(buf);
|
|
|
|
free(item->string);
|
|
|
|
item->string = xstrdup(buf);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2013-06-25 19:53:42 +04:00
|
|
|
static void normalize_argv_string(const char **var, const char *input)
|
|
|
|
{
|
|
|
|
if (!strcmp(input, "<null>"))
|
|
|
|
*var = NULL;
|
|
|
|
else if (!strcmp(input, "<empty>"))
|
|
|
|
*var = "";
|
|
|
|
else
|
|
|
|
*var = input;
|
|
|
|
|
|
|
|
if (*var && (**var == '<' || **var == '('))
|
|
|
|
die("Bad value: %s\n", input);
|
|
|
|
}
|
|
|
|
|
2016-01-12 10:57:57 +03:00
|
|
|
struct test_data {
|
|
|
|
const char *from; /* input: transform from this ... */
|
|
|
|
const char *to; /* output: ... to this. */
|
t0060: loosen overly strict expectations
The dirname() tests file were developed and tested on only the five
platforms available to the developer at the time, namely: Linux (both 32
and 64bit), Windows XP 32-bit (MSVC), MinGW 32-bit and Cygwin 32-bit.
http://pubs.opengroup.org/onlinepubs/9699919799/functions/basename.html
(i.e. the POSIX spec) says, in part:
If the string pointed to by path consists entirely of the '/'
character, basename() shall return a pointer to the string "/".
If the string pointed to by path is exactly "//", it is
implementation-defined whether "/" or "//" is returned.
The thinking behind testing precise, OS-dependent output values was to
document that different setups produce different values. However, as the
test failures on MacOSX illustrated eloquently: hardcoding pretty much each
and every setup's expectations is pretty fragile.
This is not limited to the "//" vs "/" case, of course, other inputs are
also allowed to produce multiple outputs by the POSIX specs.
So let's just test for all allowed values and be done with it. This still
documents that Git cannot rely on one particular output value in those
cases, so the intention of the original tests is still met.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-01-14 09:48:27 +03:00
|
|
|
const char *alternative; /* output: ... or this. */
|
2016-01-12 10:57:57 +03:00
|
|
|
};
|
|
|
|
|
|
|
|
static int test_function(struct test_data *data, char *(*func)(char *input),
|
|
|
|
const char *funcname)
|
|
|
|
{
|
|
|
|
int failed = 0, i;
|
|
|
|
char buffer[1024];
|
|
|
|
char *to;
|
|
|
|
|
|
|
|
for (i = 0; data[i].to; i++) {
|
|
|
|
if (!data[i].from)
|
|
|
|
to = func(NULL);
|
|
|
|
else {
|
|
|
|
strcpy(buffer, data[i].from);
|
|
|
|
to = func(buffer);
|
|
|
|
}
|
t0060: loosen overly strict expectations
The dirname() tests file were developed and tested on only the five
platforms available to the developer at the time, namely: Linux (both 32
and 64bit), Windows XP 32-bit (MSVC), MinGW 32-bit and Cygwin 32-bit.
http://pubs.opengroup.org/onlinepubs/9699919799/functions/basename.html
(i.e. the POSIX spec) says, in part:
If the string pointed to by path consists entirely of the '/'
character, basename() shall return a pointer to the string "/".
If the string pointed to by path is exactly "//", it is
implementation-defined whether "/" or "//" is returned.
The thinking behind testing precise, OS-dependent output values was to
document that different setups produce different values. However, as the
test failures on MacOSX illustrated eloquently: hardcoding pretty much each
and every setup's expectations is pretty fragile.
This is not limited to the "//" vs "/" case, of course, other inputs are
also allowed to produce multiple outputs by the POSIX specs.
So let's just test for all allowed values and be done with it. This still
documents that Git cannot rely on one particular output value in those
cases, so the intention of the original tests is still met.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-01-14 09:48:27 +03:00
|
|
|
if (!strcmp(to, data[i].to))
|
|
|
|
continue;
|
|
|
|
if (!data[i].alternative)
|
2016-01-12 10:57:57 +03:00
|
|
|
error("FAIL: %s(%s) => '%s' != '%s'\n",
|
|
|
|
funcname, data[i].from, to, data[i].to);
|
t0060: loosen overly strict expectations
The dirname() tests file were developed and tested on only the five
platforms available to the developer at the time, namely: Linux (both 32
and 64bit), Windows XP 32-bit (MSVC), MinGW 32-bit and Cygwin 32-bit.
http://pubs.opengroup.org/onlinepubs/9699919799/functions/basename.html
(i.e. the POSIX spec) says, in part:
If the string pointed to by path consists entirely of the '/'
character, basename() shall return a pointer to the string "/".
If the string pointed to by path is exactly "//", it is
implementation-defined whether "/" or "//" is returned.
The thinking behind testing precise, OS-dependent output values was to
document that different setups produce different values. However, as the
test failures on MacOSX illustrated eloquently: hardcoding pretty much each
and every setup's expectations is pretty fragile.
This is not limited to the "//" vs "/" case, of course, other inputs are
also allowed to produce multiple outputs by the POSIX specs.
So let's just test for all allowed values and be done with it. This still
documents that Git cannot rely on one particular output value in those
cases, so the intention of the original tests is still met.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-01-14 09:48:27 +03:00
|
|
|
else if (!strcmp(to, data[i].alternative))
|
|
|
|
continue;
|
|
|
|
else
|
|
|
|
error("FAIL: %s(%s) => '%s' != '%s', '%s'\n",
|
|
|
|
funcname, data[i].from, to, data[i].to,
|
|
|
|
data[i].alternative);
|
|
|
|
failed = 1;
|
2016-01-12 10:57:57 +03:00
|
|
|
}
|
|
|
|
return failed;
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct test_data basename_data[] = {
|
|
|
|
/* --- POSIX type paths --- */
|
|
|
|
{ NULL, "." },
|
|
|
|
{ "", "." },
|
|
|
|
{ ".", "." },
|
|
|
|
{ "..", ".." },
|
|
|
|
{ "/", "/" },
|
t0060: loosen overly strict expectations
The dirname() tests file were developed and tested on only the five
platforms available to the developer at the time, namely: Linux (both 32
and 64bit), Windows XP 32-bit (MSVC), MinGW 32-bit and Cygwin 32-bit.
http://pubs.opengroup.org/onlinepubs/9699919799/functions/basename.html
(i.e. the POSIX spec) says, in part:
If the string pointed to by path consists entirely of the '/'
character, basename() shall return a pointer to the string "/".
If the string pointed to by path is exactly "//", it is
implementation-defined whether "/" or "//" is returned.
The thinking behind testing precise, OS-dependent output values was to
document that different setups produce different values. However, as the
test failures on MacOSX illustrated eloquently: hardcoding pretty much each
and every setup's expectations is pretty fragile.
This is not limited to the "//" vs "/" case, of course, other inputs are
also allowed to produce multiple outputs by the POSIX specs.
So let's just test for all allowed values and be done with it. This still
documents that Git cannot rely on one particular output value in those
cases, so the intention of the original tests is still met.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-01-14 09:48:27 +03:00
|
|
|
{ "//", "/", "//" },
|
|
|
|
{ "///", "/", "//" },
|
|
|
|
{ "////", "/", "//" },
|
2016-01-12 10:57:57 +03:00
|
|
|
{ "usr", "usr" },
|
|
|
|
{ "/usr", "usr" },
|
|
|
|
{ "/usr/", "usr" },
|
|
|
|
{ "/usr//", "usr" },
|
|
|
|
{ "/usr/lib", "lib" },
|
|
|
|
{ "usr/lib", "lib" },
|
|
|
|
{ "usr/lib///", "lib" },
|
|
|
|
|
|
|
|
#if defined(__MINGW32__) || defined(_MSC_VER)
|
|
|
|
/* --- win32 type paths --- */
|
|
|
|
{ "\\usr", "usr" },
|
|
|
|
{ "\\usr\\", "usr" },
|
|
|
|
{ "\\usr\\\\", "usr" },
|
|
|
|
{ "\\usr\\lib", "lib" },
|
|
|
|
{ "usr\\lib", "lib" },
|
|
|
|
{ "usr\\lib\\\\\\", "lib" },
|
|
|
|
{ "C:/usr", "usr" },
|
|
|
|
{ "C:/usr", "usr" },
|
|
|
|
{ "C:/usr/", "usr" },
|
|
|
|
{ "C:/usr//", "usr" },
|
|
|
|
{ "C:/usr/lib", "lib" },
|
|
|
|
{ "C:usr/lib", "lib" },
|
|
|
|
{ "C:usr/lib///", "lib" },
|
|
|
|
{ "C:", "." },
|
|
|
|
{ "C:a", "a" },
|
|
|
|
{ "C:/", "/" },
|
|
|
|
{ "C:///", "/" },
|
t0060: loosen overly strict expectations
The dirname() tests file were developed and tested on only the five
platforms available to the developer at the time, namely: Linux (both 32
and 64bit), Windows XP 32-bit (MSVC), MinGW 32-bit and Cygwin 32-bit.
http://pubs.opengroup.org/onlinepubs/9699919799/functions/basename.html
(i.e. the POSIX spec) says, in part:
If the string pointed to by path consists entirely of the '/'
character, basename() shall return a pointer to the string "/".
If the string pointed to by path is exactly "//", it is
implementation-defined whether "/" or "//" is returned.
The thinking behind testing precise, OS-dependent output values was to
document that different setups produce different values. However, as the
test failures on MacOSX illustrated eloquently: hardcoding pretty much each
and every setup's expectations is pretty fragile.
This is not limited to the "//" vs "/" case, of course, other inputs are
also allowed to produce multiple outputs by the POSIX specs.
So let's just test for all allowed values and be done with it. This still
documents that Git cannot rely on one particular output value in those
cases, so the intention of the original tests is still met.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-01-14 09:48:27 +03:00
|
|
|
{ "\\", "\\", "/" },
|
|
|
|
{ "\\\\", "\\", "/" },
|
|
|
|
{ "\\\\\\", "\\", "/" },
|
2016-01-12 10:57:57 +03:00
|
|
|
#endif
|
|
|
|
{ NULL, NULL }
|
|
|
|
};
|
|
|
|
|
|
|
|
static struct test_data dirname_data[] = {
|
|
|
|
/* --- POSIX type paths --- */
|
|
|
|
{ NULL, "." },
|
|
|
|
{ "", "." },
|
|
|
|
{ ".", "." },
|
|
|
|
{ "..", "." },
|
|
|
|
{ "/", "/" },
|
t0060: loosen overly strict expectations
The dirname() tests file were developed and tested on only the five
platforms available to the developer at the time, namely: Linux (both 32
and 64bit), Windows XP 32-bit (MSVC), MinGW 32-bit and Cygwin 32-bit.
http://pubs.opengroup.org/onlinepubs/9699919799/functions/basename.html
(i.e. the POSIX spec) says, in part:
If the string pointed to by path consists entirely of the '/'
character, basename() shall return a pointer to the string "/".
If the string pointed to by path is exactly "//", it is
implementation-defined whether "/" or "//" is returned.
The thinking behind testing precise, OS-dependent output values was to
document that different setups produce different values. However, as the
test failures on MacOSX illustrated eloquently: hardcoding pretty much each
and every setup's expectations is pretty fragile.
This is not limited to the "//" vs "/" case, of course, other inputs are
also allowed to produce multiple outputs by the POSIX specs.
So let's just test for all allowed values and be done with it. This still
documents that Git cannot rely on one particular output value in those
cases, so the intention of the original tests is still met.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-01-14 09:48:27 +03:00
|
|
|
{ "//", "/", "//" },
|
|
|
|
{ "///", "/", "//" },
|
|
|
|
{ "////", "/", "//" },
|
2016-01-12 10:57:57 +03:00
|
|
|
{ "usr", "." },
|
|
|
|
{ "/usr", "/" },
|
|
|
|
{ "/usr/", "/" },
|
|
|
|
{ "/usr//", "/" },
|
|
|
|
{ "/usr/lib", "/usr" },
|
|
|
|
{ "usr/lib", "usr" },
|
|
|
|
{ "usr/lib///", "usr" },
|
|
|
|
|
|
|
|
#if defined(__MINGW32__) || defined(_MSC_VER)
|
|
|
|
/* --- win32 type paths --- */
|
|
|
|
{ "\\", "\\" },
|
|
|
|
{ "\\\\", "\\\\" },
|
|
|
|
{ "\\usr", "\\" },
|
|
|
|
{ "\\usr\\", "\\" },
|
|
|
|
{ "\\usr\\\\", "\\" },
|
|
|
|
{ "\\usr\\lib", "\\usr" },
|
|
|
|
{ "usr\\lib", "usr" },
|
|
|
|
{ "usr\\lib\\\\\\", "usr" },
|
|
|
|
{ "C:a", "C:." },
|
|
|
|
{ "C:/", "C:/" },
|
|
|
|
{ "C:///", "C:/" },
|
|
|
|
{ "C:/usr", "C:/" },
|
|
|
|
{ "C:/usr/", "C:/" },
|
|
|
|
{ "C:/usr//", "C:/" },
|
|
|
|
{ "C:/usr/lib", "C:/usr" },
|
|
|
|
{ "C:usr/lib", "C:usr" },
|
|
|
|
{ "C:usr/lib///", "C:usr" },
|
|
|
|
{ "\\\\\\", "\\" },
|
|
|
|
{ "\\\\\\\\", "\\" },
|
t0060: loosen overly strict expectations
The dirname() tests file were developed and tested on only the five
platforms available to the developer at the time, namely: Linux (both 32
and 64bit), Windows XP 32-bit (MSVC), MinGW 32-bit and Cygwin 32-bit.
http://pubs.opengroup.org/onlinepubs/9699919799/functions/basename.html
(i.e. the POSIX spec) says, in part:
If the string pointed to by path consists entirely of the '/'
character, basename() shall return a pointer to the string "/".
If the string pointed to by path is exactly "//", it is
implementation-defined whether "/" or "//" is returned.
The thinking behind testing precise, OS-dependent output values was to
document that different setups produce different values. However, as the
test failures on MacOSX illustrated eloquently: hardcoding pretty much each
and every setup's expectations is pretty fragile.
This is not limited to the "//" vs "/" case, of course, other inputs are
also allowed to produce multiple outputs by the POSIX specs.
So let's just test for all allowed values and be done with it. This still
documents that Git cannot rely on one particular output value in those
cases, so the intention of the original tests is still met.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-01-14 09:48:27 +03:00
|
|
|
{ "C:", "C:.", "." },
|
2016-01-12 10:57:57 +03:00
|
|
|
#endif
|
|
|
|
{ NULL, NULL }
|
|
|
|
};
|
|
|
|
|
2008-05-20 10:48:54 +04:00
|
|
|
int main(int argc, char **argv)
|
|
|
|
{
|
2009-02-07 18:08:30 +03:00
|
|
|
if (argc == 3 && !strcmp(argv[1], "normalize_path_copy")) {
|
2009-01-28 02:07:36 +03:00
|
|
|
char *buf = xmalloc(PATH_MAX + 1);
|
2009-02-07 18:08:30 +03:00
|
|
|
int rv = normalize_path_copy(buf, argv[2]);
|
|
|
|
if (rv)
|
|
|
|
buf = "++failed++";
|
2008-05-20 10:48:54 +04:00
|
|
|
puts(buf);
|
2009-02-07 18:08:27 +03:00
|
|
|
return 0;
|
2008-05-20 10:48:54 +04:00
|
|
|
}
|
|
|
|
|
2011-03-17 14:26:46 +03:00
|
|
|
if (argc >= 2 && !strcmp(argv[1], "real_path")) {
|
2008-05-20 10:49:00 +04:00
|
|
|
while (argc > 2) {
|
2011-03-17 14:26:46 +03:00
|
|
|
puts(real_path(argv[2]));
|
2008-05-20 10:49:00 +04:00
|
|
|
argc--;
|
|
|
|
argv++;
|
|
|
|
}
|
2009-02-07 18:08:27 +03:00
|
|
|
return 0;
|
2008-05-20 10:49:00 +04:00
|
|
|
}
|
|
|
|
|
2011-08-04 08:47:47 +04:00
|
|
|
if (argc >= 2 && !strcmp(argv[1], "absolute_path")) {
|
|
|
|
while (argc > 2) {
|
|
|
|
puts(absolute_path(argv[2]));
|
|
|
|
argc--;
|
|
|
|
argv++;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2008-05-20 10:49:26 +04:00
|
|
|
if (argc == 4 && !strcmp(argv[1], "longest_ancestor_length")) {
|
2012-10-28 20:16:24 +04:00
|
|
|
int len;
|
|
|
|
struct string_list ceiling_dirs = STRING_LIST_INIT_DUP;
|
2012-10-28 20:16:25 +04:00
|
|
|
char *path = xstrdup(argv[2]);
|
2012-10-28 20:16:24 +04:00
|
|
|
|
2012-10-28 20:16:25 +04:00
|
|
|
/*
|
|
|
|
* We have to normalize the arguments because under
|
|
|
|
* Windows, bash mangles arguments that look like
|
|
|
|
* absolute POSIX paths or colon-separate lists of
|
|
|
|
* absolute POSIX paths into DOS paths (e.g.,
|
|
|
|
* "/foo:/foo/bar" might be converted to
|
|
|
|
* "D:\Src\msysgit\foo;D:\Src\msysgit\foo\bar"),
|
|
|
|
* whereas longest_ancestor_length() requires paths
|
|
|
|
* that use forward slashes.
|
|
|
|
*/
|
|
|
|
if (normalize_path_copy(path, path))
|
|
|
|
die("Path \"%s\" could not be normalized", argv[2]);
|
2012-10-28 20:16:24 +04:00
|
|
|
string_list_split(&ceiling_dirs, argv[3], PATH_SEP, -1);
|
2012-10-28 20:16:25 +04:00
|
|
|
filter_string_list(&ceiling_dirs, 0,
|
|
|
|
normalize_ceiling_entry, NULL);
|
|
|
|
len = longest_ancestor_length(path, &ceiling_dirs);
|
2012-10-28 20:16:24 +04:00
|
|
|
string_list_clear(&ceiling_dirs, 0);
|
2012-10-28 20:16:25 +04:00
|
|
|
free(path);
|
2008-05-20 10:49:26 +04:00
|
|
|
printf("%d\n", len);
|
2009-02-07 18:08:27 +03:00
|
|
|
return 0;
|
2008-05-20 10:49:26 +04:00
|
|
|
}
|
|
|
|
|
2011-08-04 08:47:48 +04:00
|
|
|
if (argc >= 4 && !strcmp(argv[1], "prefix_path")) {
|
|
|
|
char *prefix = argv[2];
|
|
|
|
int prefix_len = strlen(prefix);
|
|
|
|
int nongit_ok;
|
|
|
|
setup_git_directory_gently(&nongit_ok);
|
|
|
|
while (argc > 3) {
|
|
|
|
puts(prefix_path(prefix, prefix_len, argv[3]));
|
|
|
|
argc--;
|
|
|
|
argv++;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2009-02-19 22:10:49 +03:00
|
|
|
if (argc == 4 && !strcmp(argv[1], "strip_path_suffix")) {
|
|
|
|
char *prefix = strip_path_suffix(argv[2], argv[3]);
|
|
|
|
printf("%s\n", prefix ? prefix : "(null)");
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2013-10-11 00:49:43 +04:00
|
|
|
if (argc == 3 && !strcmp(argv[1], "print_path")) {
|
2013-06-25 19:53:57 +04:00
|
|
|
puts(argv[2]);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2013-06-25 19:53:42 +04:00
|
|
|
if (argc == 4 && !strcmp(argv[1], "relative_path")) {
|
2013-06-25 19:53:43 +04:00
|
|
|
struct strbuf sb = STRBUF_INIT;
|
2013-06-25 19:53:42 +04:00
|
|
|
const char *in, *prefix, *rel;
|
|
|
|
normalize_argv_string(&in, argv[2]);
|
|
|
|
normalize_argv_string(&prefix, argv[3]);
|
2013-06-25 19:53:43 +04:00
|
|
|
rel = relative_path(in, prefix, &sb);
|
2013-06-25 19:53:42 +04:00
|
|
|
if (!rel)
|
|
|
|
puts("(null)");
|
|
|
|
else
|
|
|
|
puts(strlen(rel) > 0 ? rel : "(empty)");
|
2013-06-25 19:53:43 +04:00
|
|
|
strbuf_release(&sb);
|
2013-06-25 19:53:42 +04:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2016-01-12 10:57:57 +03:00
|
|
|
if (argc == 2 && !strcmp(argv[1], "basename"))
|
|
|
|
return test_function(basename_data, basename, argv[1]);
|
|
|
|
|
|
|
|
if (argc == 2 && !strcmp(argv[1], "dirname"))
|
|
|
|
return test_function(dirname_data, dirname, argv[1]);
|
|
|
|
|
2009-02-07 18:08:27 +03:00
|
|
|
fprintf(stderr, "%s: unknown function name: %s\n", argv[0],
|
|
|
|
argv[1] ? argv[1] : "(there was none)");
|
|
|
|
return 1;
|
2008-05-20 10:48:54 +04:00
|
|
|
}
|