From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] refpolicywarn/refpolicyerr
Date: Tue, 8 Nov 2011 08:39:19 -0500 [thread overview]
Message-ID: <4EB93107.5010209@tresys.com> (raw)
In-Reply-To: <201111071447.37862.russell@coker.com.au>
On 11/06/11 22:47, Russell Coker wrote:
> How long are we going to keep the refpolicywarn/refpolicyerr things around?
>
> If we are going to keep them for a long time could we get a way to make them
> break the build? Something like the -Werror option of GCC?
I assume you're referring to the deprecated interfaces. I've been removing some of the really old stuff (eg 2008 and prior), but I think we need to set official removal dates for deprecated interfaces. It'll probably be somewhere like 2 years or so from its original deprecation date. If/when CIL is finished, and refpolicy transitions to a proper high level language, the deprecated interfaces will almost certainly be shed.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2011-11-08 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 3:47 [refpolicy] refpolicywarn/refpolicyerr Russell Coker
2011-11-08 13:39 ` Christopher J. PeBenito [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=4EB93107.5010209@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.