From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [git commit] package/dust: new package
Date: Wed, 27 Jul 2022 16:43:59 +0200 [thread overview]
Message-ID: <20220727143225.6877786697@busybox.osuosl.org> (raw)
commit: https://git.buildroot.net/buildroot/commit/?id=acb02354a128ef8e4b18f2f311cd51ac6b4cb7e5
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
dust is an alternative of the command du from the Linux kernel,
written in Rust. It aims to be more intuitive and visual in order
to give the user a better view of his system's storage capacity.
Signed-off-by: Nicolas Tran <nicolas.tran@smile.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
DEVELOPERS | 1 +
package/Config.in | 1 +
package/dust/Config.in | 11 +++++++++++
package/dust/dust.hash | 3 +++
package/dust/dust.mk | 12 ++++++++++++
5 files changed, 28 insertions(+)
diff --git a/DEVELOPERS b/DEVELOPERS
index 5864601dd8..6d6f25affd 100644
--- a/DEVELOPERS
+++ b/DEVELOPERS
@@ -2188,6 +2188,7 @@ F: package/exiv2/
F: package/ofono/
N: Nicolas Tran <nicolas.tran@smile.fr>
+F: package/dust/
F: package/hyperfine/
N: Niklas Cassel <niklas.cassel@wdc.com>
diff --git a/package/Config.in b/package/Config.in
index 58ceaaa70b..9e355723d6 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -211,6 +211,7 @@ menu "Filesystem and flash utilities"
source "package/curlftpfs/Config.in"
source "package/davfs2/Config.in"
source "package/dosfstools/Config.in"
+ source "package/dust/Config.in"
source "package/e2fsprogs/Config.in"
source "package/e2tools/Config.in"
source "package/ecryptfs-utils/Config.in"
diff --git a/package/dust/Config.in b/package/dust/Config.in
new file mode 100644
index 0000000000..7b6e9304bc
--- /dev/null
+++ b/package/dust/Config.in
@@ -0,0 +1,11 @@
+config BR2_PACKAGE_DUST
+ bool "dust"
+ depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS
+ select BR2_PACKAGE_HOST_RUSTC
+ help
+ dust is an alternative written in Rust of the command "du"
+ from the Linux kernel. It aims to be more intuitive and visual
+ in order to give the user a better view of his system's
+ current storage capacity.
+
+ https://github.com/bootandy/dust.git
diff --git a/package/dust/dust.hash b/package/dust/dust.hash
new file mode 100644
index 0000000000..d4f6bff4e4
--- /dev/null
+++ b/package/dust/dust.hash
@@ -0,0 +1,3 @@
+# Locally computed
+sha256 271cc0f1978049b2dbfece633b85d4dd0184df346bd93720062c13e4332f2549 dust-0.8.1.tar.gz
+sha256 c71d239df91726fc519c6eb72d318ec65820627232b2f796219e87dcf35d0ab4 LICENSE
diff --git a/package/dust/dust.mk b/package/dust/dust.mk
new file mode 100644
index 0000000000..2cffc336a9
--- /dev/null
+++ b/package/dust/dust.mk
@@ -0,0 +1,12 @@
+################################################################################
+#
+# dust
+#
+################################################################################
+
+DUST_VERSION = 0.8.1
+DUST_SITE = $(call github,bootandy,dust,v$(DUST_VERSION))
+DUST_LICENSE = APACHE-2.0
+DUST_LICENSE_FILES = LICENSE
+
+$(eval $(cargo-package))
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2022-07-27 14:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220727143225.6877786697@busybox.osuosl.org \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.