public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: profiles/default/linux/
Date: Mon, 17 Aug 2015 18:58:44 +0000 (UTC)	[thread overview]
Message-ID: <1439450846.7444b0de8068e3392335006b7cb7c9805b761149.vapier@gentoo> (raw)

commit:     7444b0de8068e3392335006b7cb7c9805b761149
Author:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Thu Aug 13 07:27:26 2015 +0000
Commit:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Thu Aug 13 07:27:26 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7444b0de

profiles: linux: enable USE=seccomp by default

 profiles/default/linux/make.defaults | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/profiles/default/linux/make.defaults b/profiles/default/linux/make.defaults
index 7ad3bdb..be2f6a1 100644
--- a/profiles/default/linux/make.defaults
+++ b/profiles/default/linux/make.defaults
@@ -17,6 +17,9 @@ USE="berkdb crypt ipv6 ncurses nls pam readline ssl tcpd zlib"
 # make sure toolchain has sane defaults <tooclhain@gentoo.org>
 USE="${USE} fortran openmp"
 
+# Security ftw.
+USE="${USE} seccomp"
+
 # 2010/10/21 - Ole Markus With <olemarkus@gentoo.org>
 # These USE flags were originally inserted here because of PHP
 # and were later removed by me. Reinserting the USE flags again because they are


             reply	other threads:[~2015-08-17 18:58 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17 18:58 Mike Frysinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-08-23 10:40 [gentoo-commits] repo/gentoo:master commit in: profiles/default/linux/ Christian Ruppert
2015-09-03 11:04 Michael Palimaka
2015-10-29 23:44 Anthony G. Basile
2015-11-19  5:57 NP Hardass
2016-01-19  2:04 NP Hardass
2016-01-24 22:48 Matt Thode
2016-07-24 23:27 NP Hardass
2016-11-24  0:25 Matt Thode
2017-01-20 17:52 Matt Turner
2017-02-14  5:14 Brian Dolbec
2017-10-30  1:26 Mike Gilbert
2018-02-11 14:27 Jorge Manuel B. S. Vicetto
2018-02-11 14:27 Jorge Manuel B. S. Vicetto
2019-01-13 20:38 William Hubbs
2019-04-14 15:23 Aaron Bauman
2019-09-17 20:39 Patrick McLean
2019-10-15 13:27 Lars Wendler
2019-12-23 21:18 Alexey Shvetsov
2020-10-01 11:50 Tony Vroon
2020-10-01 11:52 Tony Vroon
2021-02-07  2:17 Sam James
2021-05-06  6:53 Andrey Grozin
2021-06-30 23:12 Sam James
2021-06-30 23:13 Sam James
2021-08-22 12:50 Andreas K. Hüttel
2021-09-24 21:02 Mike Gilbert
2021-09-24 21:02 Mike Gilbert
2021-12-20 19:01 Mike Gilbert
2022-01-03  5:10 Andrey Grozin
2022-02-22 17:31 Mike Gilbert
2022-06-10  6:39 Sam James
2023-01-25 18:37 Ben Kohler
2023-04-01 16:53 Sam James
2023-06-10 17:16 Sam James
2023-07-08 17:32 Andreas K. Hüttel
2023-10-02 19:32 Conrad Kostecki
2023-10-03  1:40 Sam James
2023-10-31 20:01 Mike Gilbert
2024-01-29 19:31 Matt Turner
2025-02-11 11:22 Sam James

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=1439450846.7444b0de8068e3392335006b7cb7c9805b761149.vapier@gentoo \
    --to=vapier@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