From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Jason <jason@fatpipeinc.com>
Subject: Re: audit without python?
Date: Tue, 25 Oct 2011 13:23:49 -0400 [thread overview]
Message-ID: <201110251323.49300.sgrubb@redhat.com> (raw)
In-Reply-To: <4EA6EE14.5060107@fatpipeinc.com>
On Tuesday, October 25, 2011 01:12:52 PM Jason wrote:
> Is it possible to compile and use audit without needing python? If so,
> how?
I've never considered compiling without python because its so pervasive. You can't
really have a functioning system without it inless its an appliance. And would you
want an appliance doing compiles?
You can certainly separate it out after compile in the packaging portion so that
installing it doesn't drag python in. I suppose the configure and Makefiles can be fixed
so it does not make python bindings.
-Steve
next prev parent reply other threads:[~2011-10-25 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 17:12 audit without python? Jason
2011-10-25 17:23 ` Steve Grubb [this message]
2011-10-25 17:31 ` Nathaniel Husted
2011-10-25 17:51 ` Jason
2011-10-25 18:09 ` Steve Grubb
2011-10-25 18:36 ` Steve Grubb
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=201110251323.49300.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=jason@fatpipeinc.com \
--cc=linux-audit@redhat.com \
/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