public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-vpn/tailscale/
Date: Thu, 22 Aug 2024 21:50:10 +0000 (UTC)	[thread overview]
Message-ID: <1724363090.8b92b6315a96341f3bff2a7913d55683fda8b5b6.williamh@gentoo> (raw)

commit:     8b92b6315a96341f3bff2a7913d55683fda8b5b6
Author:     Ryan Li <ryanli <AT> ryanli <DOT> org>
AuthorDate: Fri Jul 26 20:04:15 2024 +0000
Commit:     William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Thu Aug 22 21:44:50 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8b92b631

net-vpn/tailscale: Add CONFIG_CHECK="~TUN".

Closes: https://github.com/gentoo/gentoo/pull/37738
Signed-off-by: Ryan Li <ryanli <AT> ryanli.org>
Signed-off-by: William Hubbs <williamh <AT> gentoo.org>

 net-vpn/tailscale/tailscale-1.72.0.ebuild | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/net-vpn/tailscale/tailscale-1.72.0.ebuild b/net-vpn/tailscale/tailscale-1.72.0.ebuild
index 9953b94ae170..8e7f0dd0cdf3 100644
--- a/net-vpn/tailscale/tailscale-1.72.0.ebuild
+++ b/net-vpn/tailscale/tailscale-1.72.0.ebuild
@@ -2,7 +2,7 @@
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
-inherit go-module systemd tmpfiles
+inherit go-module linux-info systemd tmpfiles
 
 # These settings are obtained by running ./build_dist.sh shellvars` in
 # the upstream repo.
@@ -20,6 +20,8 @@ LICENSE="MIT"
 SLOT="0"
 KEYWORDS="~amd64 ~arm ~arm64 ~riscv ~x86"
 
+CONFIG_CHECK="~TUN"
+
 RDEPEND="net-firewall/iptables"
 BDEPEND=">=dev-lang/go-1.22"
 


             reply	other threads:[~2024-08-22 21:50 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22 21:50 William Hubbs [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-13 14:43 [gentoo-commits] repo/gentoo:master commit in: net-vpn/tailscale/ William Hubbs
2025-03-13  1:47 William Hubbs
2025-03-13  0:29 Sam James
2025-03-13  0:29 Sam James
2025-03-12 22:19 William Hubbs
2025-02-25 20:07 William Hubbs
2025-02-08  5:26 William Hubbs
2025-01-03 20:10 Sam James
2024-12-18 20:15 William Hubbs
2024-12-11  4:00 Sam James
2024-12-10 22:03 William Hubbs
2024-12-06 17:18 William Hubbs
2024-12-06 17:15 William Hubbs
2024-09-24 11:44 William Hubbs
2024-09-24 11:43 William Hubbs
2024-09-22  9:16 Sam James
2024-09-22  4:40 Sam James
2024-08-21  4:07 William Hubbs
2024-08-21  4:05 William Hubbs
2024-08-20 22:29 William Hubbs
2024-05-10 23:14 William Hubbs
2024-02-17  5:40 Sam James
2024-02-15 23:14 William Hubbs
2024-02-15 17:21 William Hubbs
2024-01-03 17:40 William Hubbs
2024-01-03 17:35 William Hubbs
2023-10-17 20:40 William Hubbs
2023-10-17 17:53 William Hubbs
2023-08-07 17:27 William Hubbs
2023-04-13 15:16 William Hubbs
2023-02-25  0:17 William Hubbs
2023-02-25  0:14 William Hubbs
2022-10-27 18:21 William Hubbs
2022-10-20 22:11 William Hubbs
2022-07-18 17:50 William Hubbs
2022-06-02 20:13 William Hubbs
2022-05-18 22:19 William Hubbs
2022-04-22  9:41 Yixun Lan
2022-04-21 16:41 William Hubbs
2022-02-27  7:47 William Hubbs
2022-02-09  0:42 Patrick McLean
2022-02-09  0:42 Patrick McLean
2021-11-29 17:44 Patrick McLean
2021-08-28 21:59 William Hubbs
2021-08-28  2:24 Sam James
2021-07-30 23:31 Sam James
2021-06-25 21:08 Patrick McLean
2021-06-21 22:27 Sam James
2021-06-21 22:26 Sam James
2021-03-07 18:02 William Hubbs
2021-01-28 23:14 William Hubbs
2021-01-28 20:19 William Hubbs
2020-12-29 16:20 William Hubbs
2020-12-21 19:53 Sam James
2020-12-20 19:26 Thomas Deutschmann
2020-12-20 16:51 Sam James
2020-12-16  4:19 William Hubbs
2020-12-15 21:49 William Hubbs
2020-12-15  2:34 William Hubbs
2020-12-15  1:58 William Hubbs
2020-12-15  1:51 William Hubbs
2020-12-15  1:51 William Hubbs
2020-05-18 17:30 William Hubbs
2020-05-14  4:11 Patrick McLean
2020-05-14  4:11 Patrick McLean
2020-04-22  1:13 Patrick McLean

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=1724363090.8b92b6315a96341f3bff2a7913d55683fda8b5b6.williamh@gentoo \
    --to=williamh@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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