All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCHv2 0/4] Separate domtrans/run interfaces for portage_fetch
Date: Wed, 14 Sep 2011 12:49:44 -0400	[thread overview]
Message-ID: <4E70DB28.4090707@tresys.com> (raw)
In-Reply-To: <20110913181932.GA29878@siphos.be>

On 09/13/11 14:19, Sven Vermeulen wrote:
> This revised patchset updates the portage interfaces to support
> portage_run_fetch and portage_domtrans_fetch, rather than including the
> support for portage_fetch_t in the regular portage_run and portage_domtrans
> interfaces.
> 
> I'm not sure how to best "mix" changes across refpolicy and
> refpolicy::contrib. If the patches are not correctly made, this was what I
> did:
> - Make changes in contrib, then format-patch to generate patches
> - Make changes in refpolicy, then format-patch to generate patches

I'm not sure what the best way is either.  The way you did it is fine.

> I notice that git also supports "adding" the commits from contrib to the
> patches in the main refpolicy, but I'm not sure that's the idea behind it
> for refpolicy.
> 
> Changes since v1
> ----------------
> 
> - Removes the portage_fetch_t calls from portage_domtrans and portage_run
> - Adds callers for portage_fetch_t (sysadm, unconfined and puppet for now)

Merged.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

      parent reply	other threads:[~2011-09-14 16:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-13 18:19 [refpolicy] [PATCHv2 0/4] Separate domtrans/run interfaces for portage_fetch Sven Vermeulen
2011-09-13 18:20 ` [refpolicy] [PATCHv2 1/4] " Sven Vermeulen
2011-09-13 18:21 ` [refpolicy] [PATCHv2 2/4] Allow puppet to call portage Sven Vermeulen
2011-09-13 18:21 ` [refpolicy] [PATCHv2 3/4] Allow sysadm_t to call all portage related services Sven Vermeulen
2011-09-13 18:22 ` [refpolicy] [PATCHv2 4/4] Allow unconfined users to call portage features Sven Vermeulen
2011-09-14 16:50   ` Christopher J. PeBenito
2011-09-14 16:49 ` 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=4E70DB28.4090707@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.