All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: SELinux List <selinux@tycho.nsa.gov>
Subject: ANN: SETools 4.0.0-alpha1
Date: Wed, 29 Oct 2014 15:43:22 -0400	[thread overview]
Message-ID: <5451435A.50809@tresys.com> (raw)

Tresys has released SETools 4.0.0-alpha1:

https://github.com/TresysTechnology/setools/releases/tag/4.0.0-alpha1

The dependence on SETools 3 has been removed.  It is tested on Python
2.7, but development will likely be transitioning to Python 3.3, as the
barriers blocking 3.3 have been addressed.

While this is still alpha code, the existing code is fairly well tested,
with 73% coverage from unit tests[1].  The core CLI tools, with the
exception of seinfo, are nearly complete.  The GUI tools have not been
started yet.

Warning: If you replace the SETools 3.x on your system, it will break
the couple of tools from sepolgen/policycoreutils that depend on SETools
(e.g. sepolicy) since the API has changed.

If you are interested in contributing, GitHub's pull request feature is
preferred for submitting patches.  Please include unit tests.

To use SETools 4, the following packages are required:
* Python 2.7
* NetworkX
* setuptools
* libselinux
* libsepol
* libbz2

To build SETools 4, the following packages are required:
* Python 2.7
* setuptools
* libselinux
* libsepol
* libbz2
* gcc
* SWIG (tested on 2.0)
* bison
* flex

[1] as reported by coverage.py, for the Python portion of SETools

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

                 reply	other threads:[~2014-10-29 19:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5451435A.50809@tresys.com \
    --to=cpebenito@tresys.com \
    --cc=selinux@tycho.nsa.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.