All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Bennett <spb@gentoo.org>
To: Karl MacMillan <kmacmill@redhat.com>
Cc: Chad Sellers <csellers@tresys.com>,
	Joshua Brindle <jbrindle@tresys.com>,
	selinux@tycho.nsa.gov, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: SELinux userspace infrastructure language
Date: Thu, 31 May 2007 21:28:31 +0100	[thread overview]
Message-ID: <20070531212831.039d6949@maya> (raw)
In-Reply-To: <1180641428.22021.34.camel@localhost.localdomain>

On Thu, 31 May 2007 15:57:08 -0400
Karl MacMillan <kmacmill@redhat.com> wrote:

> > I think there are things that are very useful for us around config
> > file parsing, general string handling, etc. Also the graph library
> > would be great for some of the analysis tasks.

This is true, though last time I looked at the boost parser libraries
(admittedly quite a few years ago) they felt more like a nice
demonstration of how to abuse certain language features in new and
interesting ways than a practical way to get things done. The other
parts I've not yet had a need to use.

> > Last time I used it I kept a private copy and only linked in what I
> > used. I guess we could limit the use to python, though, and only
> > have it as a runtime requirement for the python bindings.

Yeah, in many cases this is the only reasonable way to use it. Which is
a shame, really, because some small parts can be nice to have but
aren't worth depending on the entire thing for.

> Most of boost is just headers, so it is just a compile time
> dependency.

Another good point, though my perception here is rather skewed towards
Gentoo, where compile time dependencies are just as much of a pain, and
boost is a really big compile time depend for just a couple of headers.
That's fixed by importing small parts of it into the source tree,
though, so it's not a massive problem.

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

      parent reply	other threads:[~2007-05-31 20:28 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 17:35 SELinux userspace infrastructure language Joshua Brindle
2007-05-31 17:47 ` Karl MacMillan
2007-05-31 17:54   ` Joshua Brindle
2007-05-31 19:31     ` Karl MacMillan
2007-06-04 22:24       ` Karl MacMillan
2007-06-05  0:52         ` Joshua Brindle
2007-06-04 16:49           ` Karl MacMillan
2007-06-05 14:19             ` Stephen Smalley
2007-06-05 15:13               ` Karl MacMillan
2007-06-06 12:42                 ` Stephen Smalley
2007-06-06 14:51                   ` Karl MacMillan
2007-06-05 23:18             ` Joshua Brindle
2007-06-06 14:48               ` Karl MacMillan
2007-06-06 14:59                 ` Joshua Brindle
2007-06-06 15:18                   ` Karl MacMillan
2007-06-06 15:28                     ` Joshua Brindle
2007-06-06 16:19                       ` Stephen Bennett
2007-06-06 16:30                         ` Karl MacMillan
2007-06-06 17:07                           ` Stephen Bennett
2007-05-31 19:45     ` Stephen Bennett
2007-06-01  4:10       ` James Antill
2007-06-01 11:40         ` Stephen Bennett
2007-06-01 11:47           ` Stephen Bennett
2007-06-01 14:49         ` Karl MacMillan
2007-06-01 15:17           ` Joshua Brindle
2007-06-04 21:30       ` Help with semanage Hasan Rezaul-CHR010
2007-06-04 21:40         ` Stephen Smalley
2007-06-04 22:12           ` Hasan Rezaul-CHR010
2007-06-05 13:07             ` Stephen Smalley
2007-06-05 16:34               ` Hasan Rezaul-CHR010
2007-06-05 17:36                 ` Stephen Smalley
2007-06-05 17:51                   ` Stephen Smalley
2007-05-31 18:00   ` SELinux userspace infrastructure language Chad Sellers
2007-05-31 19:13     ` Karl MacMillan
     [not found]       ` <20070531205635.3b85f72b@maya>
     [not found]         ` <1180641092.22021.30.camel@localhost.localdomain>
     [not found]           ` <1180641428.22021.34.camel@localhost.localdomain>
2007-05-31 20:28             ` Stephen Bennett [this message]

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=20070531212831.039d6949@maya \
    --to=spb@gentoo.org \
    --cc=csellers@tresys.com \
    --cc=jbrindle@tresys.com \
    --cc=kmacmill@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --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.