From: pebenito@ieee.org (Chris PeBenito)
Date: Sat, 23 Jun 2018 11:40:40 -0400
Subject: [refpolicy] RFC: repo merge
In-Reply-To: <20180618171058.GA62119@baraddur.perfinion.com>
References: <1f7bfd8a-664a-be15-cee3-2d0ce8d82eff@ieee.org>
	<20180618171058.GA62119@baraddur.perfinion.com>
Message-ID: <092faa78-97cd-f908-e0f7-5d6ef85df642@ieee.org>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

On 06/18/2018 01:10 PM, Jason Zaman wrote:
> On Sat, Jun 16, 2018 at 10:17:41AM -0400, Chris PeBenito via refpolicy wrote:
>> I will be moving the refpolicy repo to the SELinuxProject GitHub
>> project.  While doing this, I'm considering merging the contrib repo
>> back into the main refpolicy repo.  Since this affects downstream users
>> (especially distros), I'm requesting comments.
>>
>> The way I see it, there are a few options, in increasing disruptiveness:
>>
>> * keep as-is (no repo structure change)
>> * move modules in contrib to policy/modules/contrib in the main repo
>> * move modules in contrib to policy/modules/services,
>> policy/modules/apps, etc. in the main repo, where it makes most sense
> 
> I'd like them merged in too, we have them merged in our downstream
> gentoo policy repo. I think moving things into other dirs would make
> sense too. Afterall, everything was contributed so thats kind of a
> meaningless dir. Please do one commit that just merges
> contrib in without any other changes. Then later commits can move things
> around then its easier for me to fix things up in our repo.

I ended up doing this as part of the repo move.

-- 
Chris PeBenito