public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sven Vermeulen" <sven.vermeulen@siphos.be>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-docs:master commit in: html/selinux/
Date: Sun, 10 Apr 2011 07:49:30 +0000 (UTC)	[thread overview]
Message-ID: <02d07bbfde01f5f222202bcd73fc208b66a74ded.SwifT@gentoo> (raw)

commit:     02d07bbfde01f5f222202bcd73fc208b66a74ded
Author:     Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be>
AuthorDate: Sun Apr 10 07:48:50 2011 +0000
Commit:     Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be>
CommitDate: Sun Apr 10 07:48:50 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-docs.git;a=commit;h=02d07bbf

Update previews

---
 html/selinux/hb-using-install.html |   19 ++++++++++++++++++-
 1 files changed, 18 insertions(+), 1 deletions(-)

diff --git a/html/selinux/hb-using-install.html b/html/selinux/hb-using-install.html
index 416b00b..1e12fc6 100644
--- a/html/selinux/hb-using-install.html
+++ b/html/selinux/hb-using-install.html
@@ -76,6 +76,23 @@ Make sure to include layman's <span class="path" dir="ltr">make.conf</span> in y
 <span class="code-input">source /var/lib/layman/make.conf</span>
 </pre></td></tr>
 </table>
+<p class="secthead"><a name="doc_chap1_sect1">Switching to Python 2</a></p>
+<p>
+For now, the SELinux management utilities are not compatible with Python 3 so
+we recommend to switch to Python 2 until the packages are updated and fixed.
+</p>
+<a name="doc_chap1_pre1"></a><table class="ntable" width="100%" cellspacing="0" cellpadding="0" border="0">
+<tr><td bgcolor="#7a5ada"><p class="codetitle">Code Listing1.1: Switching to python 2</p></td></tr>
+<tr><td bgcolor="#eeeeff" align="left" dir="ltr"><pre>
+~# <span class="code-input">eselect python list</span>
+Available Python interpreters:
+  [1]   python2.7
+  [2]   python3.1 *
+
+~# <span class="code-input">eselect python set 1</span>
+~# <span class="code-input">source /etc/profile</span>
+</pre></td></tr>
+</table>
 <p class="secthead"><a name="doc_chap1_sect1">Optional: Setting the /tmp context</a></p>
 <p>
 If your <span class="path" dir="ltr">/tmp</span> location is a tmpfs-mounted file system, then you need
@@ -515,7 +532,7 @@ made.
 </p>
 </td>
 <td width="1%" bgcolor="#dddaec" valign="top"><table border="0" cellspacing="4px" cellpadding="4px">
-<tr><td class="topsep" align="center"><p class="alttext">Updated March 9, 2011</p></td></tr>
+<tr><td class="topsep" align="center"><p class="alttext">Updated April 10, 2011</p></td></tr>
 <tr lang="en"><td align="center" class="topsep">
 <p class="alttext"><b>Donate</b> to support our development efforts.
         </p>



             reply	other threads:[~2011-04-10  7:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-10  7:49 Sven Vermeulen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-06-07 19:26 [gentoo-commits] proj/hardened-docs:master commit in: html/selinux/ Sven Vermeulen
2011-06-02 12:02 Sven Vermeulen
2011-05-31 20:28 Sven Vermeulen
2011-05-24 20:42 Sven Vermeulen
2011-02-19 17:01 Francisco Blas Izquierdo Riera
2011-02-19  3:21 Francisco Blas Izquierdo Riera
2011-02-19  3:12 Francisco Blas Izquierdo Riera

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=02d07bbfde01f5f222202bcd73fc208b66a74ded.SwifT@gentoo \
    --to=sven.vermeulen@siphos.be \
    --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