From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] new refpolicy release
Date: Mon, 25 Jul 2011 08:12:25 -0400 [thread overview]
Message-ID: <4E2D5DA9.7060901@tresys.com> (raw)
In-Reply-To: <201107241559.02111.russell@coker.com.au>
On 07/24/11 01:59, Russell Coker wrote:
> http://oss.tresys.com/projects/refpolicy/wiki/DownloadRelease
>
> It seems that the latest refpolicy release is from 2010. Are there plans for
> a new one soon?
Yes, I'm doing one this week.
> I am just uploading what I plan to be the last 20100524 based release for
> Debian/Unstable. I will try to get stuff from that included in Debian/Squeeze
> (the current stable release) but apart from that I'm finished with 20100524.
>
> I'm not really keen on getting a 6 month old release as I've got a heap of
> changes, some of which should go upstream. I'd like to get a new upstream
> release to base on for the purpose of sorting out all the patches.
>
> One option I'm considering is taking the current git tree, calling it
> 20110724, and using it as the base for Debian development.
>
> As an aside, what's the status of systemd policy?
There isn't one upstream. The last time it was discussed, I suggested
that it was so different and did so many more things that it should
probably be its own module. I haven't heard or seen anything since then.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2011-07-25 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 5:59 [refpolicy] new refpolicy release Russell Coker
2011-07-25 12:12 ` Christopher J. PeBenito [this message]
2011-07-25 12:17 ` Dominick Grift
2011-07-25 12:39 ` Russell Coker
2011-07-25 12:53 ` Dominick Grift
2011-07-25 13:31 ` Dominick Grift
2011-07-25 14:51 ` Daniel J Walsh
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=4E2D5DA9.7060901@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.