-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have gotten a lot of fedora contrib policy to compile against the
latest refpolicy (base). Now the question is how do we go about
getting the contrib policy merged into refpolicy.
Once we have done a good portion of this, we can start looking at
merging in more of the changes between current fedora policy base and
refpolicy base.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7XtS0ACgkQrlYvE4MpobMSoQCg0axhvL30lvoGBs8gcOe+tDYp
FDQAn3/gWs8BgH19N3jtBKiaNTweVEFO
=rYMo
-----END PGP SIGNATURE-----
On 12/01/11 12:11, Daniel J Walsh wrote:
> I have gotten a lot of fedora contrib policy to compile against the
> latest refpolicy (base). Now the question is how do we go about
> getting the contrib policy merged into refpolicy.
>
> Once we have done a good portion of this, we can start looking at
> merging in more of the changes between current fedora policy base and
> refpolicy base.
You can commit it. If you're worried about it showing up too soon in the base repo, the revision of contrib is pinned in the base repo, so it won't show up in the checkouts of the full repo unless you go into contrib and pull HEAD.
Alternatively, we get get an ACK on them before you commit it.
--
Chris PeBenito
Tresys Technology, LLC
http://www.tresys.com | oss.tresys.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/05/2011 08:57 AM, Christopher J. PeBenito wrote:
> On 12/01/11 12:11, Daniel J Walsh wrote:
>> I have gotten a lot of fedora contrib policy to compile against
>> the latest refpolicy (base). Now the question is how do we go
>> about getting the contrib policy merged into refpolicy.
>>
>> Once we have done a good portion of this, we can start looking
>> at merging in more of the changes between current fedora policy
>> base and refpolicy base.
>
> You can commit it. If you're worried about it showing up too soon
> in the base repo, the revision of contrib is pinned in the base
> repo, so it won't show up in the checkouts of the full repo unless
> you go into contrib and pull HEAD.
>
> Alternatively, we get get an ACK on them before you commit it.
>
I have no problem checking any of these in, although i would like to
get someone to at least ack the change. Also some of the patches
included changes to upstream, either missing interfaces or additional
port definitions.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7dE7cACgkQrlYvE4MpobNBowCfcQJCitBYrrE3BDdiwD7a8BVq
gb4An3uwynX+sjoDbk/5cj5P1YYT3OeS
=q/Yy
-----END PGP SIGNATURE-----