From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: bazel-4.1.0
Date: Sat, 04 Jun 2022 04:09:13 +0200 [thread overview]
Message-ID: <20220604020913.JApvscW_6j6XU_kox6ShJZOmPeoMHYwagNlKcDllWzI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31382@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
There's a closed pull request on the void-packages repository
New package: bazel-4.1.0
https://github.com/void-linux/void-packages/pull/31382
Description:
<!-- Mark items with [x] where applicable -->
#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR
#### Comments
I don't really know anything about bazel. I just wanted to add it because anki uses it as build system in the newer updates.
Officially, Java is said to be an [optional dependency](https://docs.bazel.build/versions/4.1.0/install-ubuntu.html#step-3-install-a-jdk-optional), however besides `bazel --version`, nothing really seems to work without java. Should I add it as a dependency? (Might be stupid question, I'm new ;P).
#### ~WIP: I'm gonna try to update anki too.~
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
next prev parent reply other threads:[~2022-06-04 2:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 22:13 [PR PATCH] " Filius-Patris
2021-06-10 0:40 ` [PR REVIEW] " ericonr
2021-06-10 0:40 ` ericonr
2021-06-10 7:02 ` [PR PATCH] [Updated] [WIP] " Filius-Patris
2021-06-10 7:41 ` fosslinux
2021-06-10 7:42 ` fosslinux
2021-06-10 21:29 ` [PR PATCH] [Updated] " Filius-Patris
2021-06-11 9:22 ` Filius-Patris
2021-06-11 15:39 ` [PR PATCH] [Updated] " Filius-Patris
2021-06-11 15:39 ` Filius-Patris
2021-06-11 15:56 ` Filius-Patris
2022-01-06 21:47 ` TobTobXX
2022-05-21 2:00 ` github-actions
2022-06-04 2:09 ` github-actions [this message]
2023-11-23 12:02 ` Luciogi
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=20220604020913.JApvscW_6j6XU_kox6ShJZOmPeoMHYwagNlKcDllWzI@z \
--to=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).