From: Joshua Brindle <jbrindle@tresys.com>
To: William Roberts <bill.c.roberts@gmail.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, <selinux@tycho.nsa.gov>,
Joman Chu <jcchu@tycho.ncsc.mil>
Subject: Re: seandroid and policy version
Date: Tue, 18 Sep 2012 15:10:24 -0400 [thread overview]
Message-ID: <5058C720.7000202@tresys.com> (raw)
In-Reply-To: <CAFftDdqWeUa1gTvrodNj3V7a7ggAwk1wNz1hOCTfLxdop8X=jQ@mail.gmail.com>
Oh right, the precedence in this build system gets me sometimes...
William Roberts wrote:
> Isn't that what ?= will let you do since it defers expansion? Again, I
> am no make guru...
>
> On Tue, Sep 18, 2012 at 12:04 PM, Joshua Brindle <jbrindle@tresys.com
> <mailto:jbrindle@tresys.com>> wrote:
>
> Stephen Smalley wrote:
>
> Attached are patches for libselinux and sepolicy to drop the policy
> version suffix. We still force generation of a version 24 policy by
> default, although this can be overridden via make command-line or
> environment setting (e.g. export POLICYVERS=26). Does this seem
> sane?
> Note that seandroid-4.0.4 requires changes to system/core as
> well, so
> this only fixes it for master and 4.1.1.
>
>
> Looks fine to me. Any chance that POLICYVERS could be set in a
> device makefile? Since you'll know what kernel you are using to
> build a particular device it would be nice to set it there and not
> have to figure out/remember what version each device uses.
>
>
>
>
> --
> Respectfully,
>
> William C Roberts
>
>
--
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:[~2012-09-18 19:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 0:07 seandroid and policy version Joshua Brindle
2012-07-11 12:50 ` Stephen Smalley
2012-07-11 19:45 ` Joshua Brindle
2012-07-11 19:49 ` Stephen Smalley
2012-09-18 17:33 ` Stephen Smalley
2012-09-18 17:40 ` Joshua Brindle
2012-09-18 17:43 ` Stephen Smalley
2012-09-18 17:56 ` Joshua Brindle
2012-09-18 18:21 ` Stephen Smalley
2012-09-18 17:46 ` William Roberts
2012-09-18 17:50 ` Stephen Smalley
2012-09-18 17:54 ` William Roberts
2012-09-18 17:57 ` William Roberts
2012-09-18 18:10 ` Stephen Smalley
2012-09-18 18:15 ` Stephen Smalley
2012-09-18 18:25 ` William Roberts
2012-09-18 18:26 ` William Roberts
2012-09-18 18:52 ` Stephen Smalley
2012-09-18 18:59 ` William Roberts
2012-09-18 19:04 ` Joshua Brindle
2012-09-18 19:07 ` William Roberts
2012-09-18 19:10 ` 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=5058C720.7000202@tresys.com \
--to=jbrindle@tresys.com \
--cc=bill.c.roberts@gmail.com \
--cc=jcchu@tycho.ncsc.mil \
--cc=sds@tycho.nsa.gov \
--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.