From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Syntax fixes in contrib
Date: Tue, 2 Dec 2014 10:31:38 -0500 [thread overview]
Message-ID: <547DDB5A.3000307@tresys.com> (raw)
In-Reply-To: <1416983956-8770-1-git-send-email-jason@perfinion.com>
On 11/26/2014 1:38 AM, Jason Zaman wrote:
> I was going through the policy and adding all the _admin interfaces to sysadm
> in the gentoo policy and hit quite a number of syntax errors. They are mostly
> just typos and missing types in gen_require.
>
> The last two remove the _role interface to not be called from _admin since the
> the _role is already called from in the role definitions and there is a
> conflict if it gets called twice so removing it from the _admin interface
> seemed reasonable. Commented them out and wrote a note above. Would it instead
> be preferred if i just removed it completely?
At first I wanted it removed, but then decided it's fine to keep the
comments, so we don't add it back in at some point in the future. Or
maybe it will work in the future, so we can add it back.
This set is merged.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2014-12-02 15:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 6:38 [refpolicy] Syntax fixes in contrib Jason Zaman
2014-11-26 6:38 ` [refpolicy] [PATCH 01/18] ccs: syntax errors in ccs_admin interface Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 02/18] condor: syntax error in condor_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 03/18] distcc: syntax error in distcc_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 04/18] ftp: syntax error in ftp_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 05/18] kerberos: syntax error in kerberos_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 06/18] kismet: syntax error in kismet_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 07/18] nut: syntax error in nut_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 08/18] prelude: syntax error in prelude_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 09/18] psad: syntax error in psad_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 10/18] quota: syntax error in quota_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 11/18] rpcbind: syntax error in rpcbind_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 12/18] rpm: syntax error in rpm_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 13/18] systemtap: syntax error in stapserver_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 14/18] svnserve: syntax error in svnserve_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 15/18] uptime: syntax error in uptime_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 16/18] zabbix: syntax error in zabbix_admin Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 17/18] remove pyzor_role() from pyzor_admin() Jason Zaman
2014-11-26 6:39 ` [refpolicy] [PATCH 18/18] remove spamassassin_role() from spamassassin_admin() Jason Zaman
2014-12-02 15:31 ` Christopher J. PeBenito [this message]
2014-12-02 16:15 ` [refpolicy] Syntax fixes in contrib Dominick Grift
2014-12-02 18:17 ` Jason Zaman
2014-12-03 9:27 ` Miroslav Grepl
2014-12-03 12:33 ` Jason Zaman
2014-12-03 14:33 ` Dominick Grift
2014-12-03 14:44 ` Christopher J. PeBenito
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=547DDB5A.3000307@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.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 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.