All of lore.kernel.org
 help / color / mirror / Atom feed
From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH/RFC v3] Introduce xdg types
Date: Tue, 1 May 2012 09:31:22 +0200	[thread overview]
Message-ID: <20120501073122.GC32060@siphos.be> (raw)
In-Reply-To: <4EC17B88.1040006@tresys.com>

On Mon, Nov 14, 2011 at 03:35:20PM -0500, Christopher J. PeBenito wrote:
> > (1.) Enhance userdom_user_home_dir_filetrans with a fourth argument
> >      (filename) and use that in its filetrans_pattern() call
> > (2.) Enhance xdg.if with the xdg_*_home_filetrans statements that accomplish
> >      something like 
> >        userdom_user_home_dir_filetrans($1, xdg_cache_home_t, dir, ".cache")
> >      for the xdg_cache_home_filetrans (others very related)
> 
> These two are fine.  I've attached my working patch for interfaces with optional 
> parameters to support name filetrans.  I'm trying to decide (with CIL in mind) if
> we really want interfaces with optional parameters.

Got your mind settled yet?

I noticed that the filetrans_pattern() definition supports the fifth
argument (as an optional parameter). Is it okay if we apply your patch
(except for the filetrans_pattern() part) and continue from there?

Wkr,
	Sven Vermeulen

  parent reply	other threads:[~2012-05-01  7:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 14:06 [refpolicy] [PATCH/RFC v3] Introduce xdg types Sven Vermeulen
2011-11-13 20:33 ` Sven Vermeulen
2011-11-14 20:35   ` Christopher J. PeBenito
2011-11-15  7:33     ` Sven Vermeulen
2011-11-15 14:23       ` Christopher J. PeBenito
2012-05-01  7:31     ` Sven Vermeulen [this message]
2012-05-10 13:57       ` 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=20120501073122.GC32060@siphos.be \
    --to=sven.vermeulen@siphos.be \
    --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.