busybox-w32/debianutils, branch manifest

Merge branch 'busybox' into merge

2018-05-13T07:15:58+00:00

tart_stop_daemon: another fix to disabled OLDER_VERSION_OF_X code

2018-04-13T23:29:01+00:00

Signed-off-by: Denys Vlasenko

start_stop_daemon: fix normally disabled OLDER_VERSION_OF_X code

2018-04-13T23:27:05+00:00

Signed-off-by: Denys Vlasenko

Merge branch 'busybox' into merge

2018-04-09T07:50:34+00:00

libbb.h: always include sys/resource.h

2018-04-08T15:23:27+00:00

Signed-off-by: Denys Vlasenko

pipe_progress: add help text

2018-04-08T07:17:17+00:00

win32: additional improvements to handling of executables

2018-02-28T20:23:18+00:00

Consistent processing of file extensions, as described in the previous commit, has been applied to the 'which' applet and the functions find_executable and mingw_spawn_interpreter. In spawnveq check that the file to be executed exists and is executable, and ensure that it won't have any extensions added by spawnve. It's intended that all files passed to spawnve should have their names fully specified. If this isn't the case the tests here will cause errors which will need to be fixed.

win32: move detection of file formats to stat(2)

2018-02-26T20:39:23+00:00

Move the code to detect shell scripts and binary executables from mingw_access to a separate function, has_exec_format. Call this function in do_lstat to decide whether to set the executable bits in the file mode. This will slow down stat but has a couple of advantages: - shell scripts are highlighted in ls output - the test applet can use stat(2) to detect executable files The new function is used to handle another corner case in spawnveq: binary executables without the usual .exe extension are only run by spawnve if the file name ends with '.'. Two minor changes: - file_is_win32_executable has been renamed add_win32_extension to clarify what it does - a call to file_is_executable has been removed from find_command in ash as it resulted in unhelpful error messages.

which: treat busybox as a special case

2018-02-13T10:52:43+00:00

Busybox knows the path to its own executable even if it isn't on PATH. Treat this as a special case and print the path. `which busybox` is used in testsuite/busybox.tests

Merge branch 'busybox' into merge

2018-02-13T09:44:44+00:00