Github messages for voidlinux
 help / color / mirror / Atom feed
From: knusbaum <knusbaum@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gradle: update to 7.3.3.
Date: Thu, 20 Jan 2022 22:40:31 +0100	[thread overview]
Message-ID: <20220120214031.479S300GNTxPlXpKnH8WV8xWuWOD4bDKzPCWBsDkBGs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34746@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 785 bytes --]

New comment by knusbaum on void-packages repository

https://github.com/void-linux/void-packages/pull/34746#issuecomment-1017936489

Comment:
Genuine question: Is there a particular reason we want to upgrade `gradle`? It seems to make certain packages more difficult to build, requiring patches for `freerouting`.

Void is rolling-release, but ["focuses on stability, rather than on being bleeding-edge"](https://voidlinux.org/). What do we get from this upgrade?

That said, the recent `apache-jmeter` update (https://github.com/void-linux/void-packages/pull/35114) causes it to build with the provided `gradlew` script, removing its dependence on `gradle`. (I'm removing `gradle` as a dependency altogether in #35147) You should be able to upgrade `gradle` without affecting it.

  parent reply	other threads:[~2022-01-20 21:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29  2:23 [PR PATCH] " unspecd
2022-01-13 20:32 ` Piraty
2022-01-13 20:32 ` Piraty
2022-01-14 17:45 ` [PR PATCH] [Updated] " unspecd
2022-01-14 17:48 ` unspecd
2022-01-14 19:32 ` unspecd
2022-01-14 20:25 ` unspecd
2022-01-16 17:15 ` Piraty
2022-01-20 21:18 ` knusbaum
2022-01-20 21:21 ` knusbaum
2022-01-20 21:40 ` knusbaum [this message]
2022-01-21  7:38 ` [PR PATCH] [Updated] " unspecd
2022-01-29 10:22 ` unspecd
2022-01-30 21:49 ` [PR PATCH] [Closed]: " Piraty

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=20220120214031.479S300GNTxPlXpKnH8WV8xWuWOD4bDKzPCWBsDkBGs@z \
    --to=knusbaum@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    --subject='Re: gradle: update to 7.3.3.' \
    /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

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).