From: Steve Lawrence <slawrence@tresys.com>
To: Sven Vermeulen <sven.vermeulen@siphos.be>,
SELinux <selinux@tycho.nsa.gov>
Subject: Re: SELinux Userspace Release: 20140826-rc5
Date: Thu, 6 Nov 2014 13:59:10 -0500 [thread overview]
Message-ID: <545BC4FE.80507@tresys.com> (raw)
In-Reply-To: <CAPzO=Nw+JszpR=FoNenH43k4cihg7pnEhecA2MyLzc9qJJcR7A@mail.gmail.com>
On 11/06/2014 01:45 PM, Sven Vermeulen wrote:
> On Oct 29, 2014 4:41 PM, "Steve Lawrence" <slawrence@tresys.com> wrote:
>>
>> The fifth release candidate for the next release of SELinux Userspace
>> [1] is now available.
> [...]
>> Please give this a test and let us know if you find any problems.
>
> I noticed that the semodule listing command does no longer include the
> module version - instead focus is now on the priority. Is this deliberate?
>
> Wkr,
> Sven Vermeulen
>
Yes, with the move to source policies and high level languages, the
concept of module versions was remove. High level languages may still
provide there own mechanism of module versioning if it makes sense (e.g.
pp modules still have versions in them), but libsemanage no longer uses
these for anything. This is also the reason for deprecating the semodule
--upgrade option.
- Steve
prev parent reply other threads:[~2014-11-06 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 15:34 SELinux Userspace Release: 20140826-rc5 Steve Lawrence
2014-11-02 15:17 ` Sven Vermeulen
2014-11-03 13:36 ` Steve Lawrence
2014-11-04 18:08 ` Sven Vermeulen
2014-11-04 20:26 ` James Carter
2014-11-06 14:12 ` Steve Lawrence
2014-11-06 14:19 ` James Carter
2014-11-06 18:45 ` Sven Vermeulen
2014-11-06 18:59 ` Steve Lawrence [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=545BC4FE.80507@tresys.com \
--to=slawrence@tresys.com \
--cc=selinux@tycho.nsa.gov \
--cc=sven.vermeulen@siphos.be \
/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.