From: Joshua Brindle <method@manicmethod.com>
To: Christopher Pardy <cpardy@redhat.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: adding human understandable, and translatable description support to selinux
Date: Tue, 21 Jul 2009 13:55:58 -0400 [thread overview]
Message-ID: <4A66012E.60801@manicmethod.com> (raw)
In-Reply-To: <4A64B6D4.6070205@redhat.com>
Christopher Pardy wrote:
>> Did you forget to do reply to all?
>>
>
> yes!
>
> If that's the best way to go fine, however the xml file is only
> generated when I acutually compile the modules if I install a module
> through semanage any data that module adds will be left out. I
> certainly wouldn't be opposed to extending policy.xml as part of this
> but there needs to be a way for installed modules to work too.
> Additionally if we're going to continue the trend of using policy.xml
> for management rather than development we really should move it.
>
One of the things that we want CIL to do is have the ability to embed
documentation for purposes such as debugging into the language. This would allow
the documentation to make it all the way into the module store and would be
retrievable by tools.
For reference we started talking about CIL here:
http://marc.info/?l=selinux&m=124784581623125&w=2
though we haven't gotten very far in the discussion.
--
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.
prev parent reply other threads:[~2009-07-21 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 14:34 adding human understandable, and translatable description support to selinux Christopher Pardy
2009-07-20 17:04 ` Remmolt G. Zwartsenberg
2009-07-20 17:27 ` Christopher J. PeBenito
[not found] ` <4A64ADA3.6020105@redhat.com>
[not found] ` <1248114027.23783.725.camel@gorn>
2009-07-20 18:26 ` Christopher Pardy
2009-07-20 19:30 ` Daniel J Walsh
2009-07-21 17:55 ` Joshua Brindle [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=4A66012E.60801@manicmethod.com \
--to=method@manicmethod.com \
--cc=cpardy@redhat.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.