staging/pepe2k/tools/e2fsprogs, branch master

tools/e2fsprogs: update to 1.47.2

2025-01-11T21:24:24Z

Release information (not yet published): https://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.47.2 Signed-off-by: John Audia Link: https://github.com/openwrt/openwrt/pull/17499 Signed-off-by: Hauke Mehrtens

tools: e2fsprogs: bypass libuuid check

2024-09-26T09:08:23Z

The check is the wrong way around. It uses AC_CHECK_LIBS and then pkg-config, probably because the latter is a second class citizen. Just bypass it. pkg-config gets used anyway. Signed-off-by: Rosen Penev Link: https://github.com/openwrt/openwrt/pull/16480 Link: https://github.com/openwrt/openwrt/pull/16480 Link: https://github.com/openwrt/openwrt/pull/16480 Signed-off-by: Robert Marko

tools: e2fsprogs: drop e2fsck patch

2024-09-25T17:53:13Z

After digging in the history of the e2fsck exit code patch, it seems like there is no reason for us to carry this patch so lets drop it. Link: https://github.com/openwrt/openwrt/pull/16500 Signed-off-by: Robert Marko

tools: e2fsprogs: pass --with-crond-dir=no instead of patching

2024-09-25T17:53:13Z

Currently, e2fsprogs is being patched to avoid detecting host crond, but instead of doing that we can simply pass --with-crond-dir=no as an argument and drop the patch. Link: https://github.com/openwrt/openwrt/pull/16500 Signed-off-by: Robert Marko

tools: e2fsprogs: drop the e4defrag patch

2024-09-25T17:53:13Z

Considering that this patch to not build e4defrag was added 12 years ago because: Compilation fails on older systems due to missing syscalls I think its safe to say that enough time is passed so that whatever those older systems were are either updated or not used anymore so lets drop the patch. Link: https://github.com/openwrt/openwrt/pull/16500 Signed-off-by: Robert Marko

tools/e2fsprogs: fixup STAGING_DIR_HOST path evaluation in shell scripts

2024-07-02T12:04:49Z

We have to use curly braces on the exported STAGING_DIR_HOST env variable, instead of evaluating it directly as we are not in Make but a separate shell script. Otherwise it would fail with: staging_dir/host/bin/compile_et: line 6: STAGING_DIR_HOST: command not found staging_dir/host/bin/mk_cmds: line 5: STAGING_DIR_HOST: command not found And so when krb5 tries to build it will fail as compile_et and mk_cmds will return an error. Fixes: 55bda9863dd0 ("tools/e2fsprogs: fix shell scripts under SDK") Link: https://github.com/openwrt/openwrt/pull/15854 Signed-off-by: Robert Marko

tools/e2fsprogs: fix shell scripts under SDK

2024-06-30T17:05:21Z

7c32295b0036be425ba0cd527eb06316a87d0ec0 exposed a problem where the SDK builds these shell scripts with a nonsensical absolute path for the DIR variable. Use sed to patch in $STAGING_DIR_HOST. Also remove PKG_RELEASE as that is nonsensical for tools. Signed-off-by: Rosen Penev Link: https://github.com/openwrt/openwrt/pull/15841 Signed-off-by: Robert Marko

tools: e2fsprogs: use standard make uninstall

2024-06-26T09:21:04Z

There is no need to manually only remove 2 binaries during cleanup and leave rest of the e2fsprogs installed stuff untouched, so instead use make uninstall to do the cleanup. Link: https://github.com/openwrt/openwrt/pull/15806 Signed-off-by: Robert Marko

tools: e2fsprogs: use libuuid provided by util-linux

2024-06-26T09:21:04Z

We are now using util-linux to provide libuuid so disable building it in e2fsprogs and simply use the util-linux provided one. Disabling libuuid removes the need for custom install recipe. Link: https://github.com/openwrt/openwrt/pull/15806 Signed-off-by: Robert Marko

tools: prefer gz or bz2 tarballs

2024-04-06T09:24:18Z

In the light of recent XZ events, and fundamental XZ issues lets work on moving away from using XZ. So, use gz compressed tarballs as sources whenever possible. dwarves only offers bz2 compressed tarballs, so use those as size difference is minor compared to XZ. Signed-off-by: Robert Marko dwarves