From: n1c00o <n1c00o@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: bazel-buildtools-5.1.0
Date: Sun, 21 Aug 2022 20:47:21 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38813@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1567 bytes --]
There is a new pull request by n1c00o against master on the void-packages repository
https://github.com/n1c00o/void-packages feat/bazel-buildtools
https://github.com/void-linux/void-packages/pull/38813
New package: bazel-buildtools-5.1.0
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- x86_64-musl
- Should support cross compilation using the Go standard toolchain
> Note: As I specified a few weeks ago in <https://github.com/void-linux/void-packages/pull/38207>, I decided to release the different Bazel buildtools into a single package to avoid polluting the repository, since these tools are often installed together.
> Note: The package is named `bazel-buildtools` to be clear that it is for Bazel, since a lot of ecosystems do have tools under the name "buildtools".
> Note: This is not a subpackage of `bazel` (unpublished yet) since they do not directly require Bazel and building Bazel from source is very long, which could be annoying for people which only needs the buildtools (since a subpackage is only executed after the main package's installation phase.
A patch file from https://github.com/void-linux/void-packages/pull/38813.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-feat/bazel-buildtools-38813.patch --]
[-- Type: text/x-diff, Size: 1807 bytes --]
From bf67a2384a4a890fa6d5e3cba70e1c1b46b5f26c Mon Sep 17 00:00:00 2001
From: n1c00o <git.n1c00o@gmail.com>
Date: Sun, 21 Aug 2022 20:41:18 +0200
Subject: [PATCH] New package: bazel-buildtools-5.1.0
added common bazel tool such as buildifier and buildozer into a single package ready to be shipped
---
srcpkgs/bazel-buildtools/template | 35 +++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
create mode 100644 srcpkgs/bazel-buildtools/template
diff --git a/srcpkgs/bazel-buildtools/template b/srcpkgs/bazel-buildtools/template
new file mode 100644
index 000000000000..36ae3535c112
--- /dev/null
+++ b/srcpkgs/bazel-buildtools/template
@@ -0,0 +1,35 @@
+# Template file for 'bazel-buildtools'
+pkgname=bazel-buildtools
+version=5.1.0
+revision=1
+wrksrc="buildtools-${version}"
+hostmakedepends="go"
+short_desc="Bazel BUILD file formatter and editor"
+maintainer="n1c00o <git.n1c00o@gmail.com>"
+license="Apache-2.0"
+homepage="https://github.com/bazelbuild/buidtools"
+distfiles="https://github.com/bazelbuild/buildtools/archive/refs/tags/${version}.tar.gz"
+checksum="e3bb0dc8b0274ea1aca75f1f8c0c835adbe589708ea89bf698069d0790701ea3"
+
+do_build() {
+ mkdir _output
+
+ # A command line tool to determine any unused dependencies in java_library targets.
+ # Standard formatting and linting tool for Bazel BUILD files.
+ # Standard tool to apply bulk actions on Bazel BUILD files.
+ for t in "unused_deps" "buildifier" "buildozer"; do
+ go build -p "$XBPS_MAKEJOBS" -o "_output/$t" ./"$t"
+ done
+}
+
+do_install() {
+ vbin _output/unused_deps unused_deps
+ vdoc ./unused_deps/README.md unused_deps.md
+
+ vbin _output/buildifier buildifier
+ vdoc ./buildifier/README.md buildifier.md
+ vdoc WARNINGS.md
+
+ vbin _output/buildozer buildozer
+ vdoc ./buildozer/README.md buildozer.md
+}
next reply other threads:[~2022-08-21 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 18:47 n1c00o [this message]
2022-08-21 22:43 ` [PR REVIEW] " classabbyamp
2022-08-21 22:43 ` classabbyamp
2022-08-21 22:43 ` classabbyamp
2022-08-22 10:20 ` n1c00o
2022-08-22 10:20 ` n1c00o
2022-08-22 10:28 ` [PR PATCH] [Updated] " n1c00o
2022-08-22 10:29 ` [PR REVIEW] " n1c00o
2022-08-23 12:06 ` [PR PATCH] [Updated] " n1c00o
2022-08-23 12:06 ` n1c00o
2022-11-28 2:04 ` github-actions
2022-11-29 15:53 ` n1c00o
2022-11-29 15:53 ` [PR PATCH] [Closed]: " n1c00o
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38813@inbox.vuxu.org \
--to=n1c00o@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).