[Buildroot] [PATCH 1/1] refpolicy: bump to 2.20170805

[Matthew Weber]

Adam,

On Sun, Nov 5, 2017 at 11:34 AM, Adam Duskett <aduskett at gmail.com> wrote:
>
> Hello;
>
> On Fri, Nov 3, 2017 at 1:56 PM, Thomas Petazzoni
> <thomas.petazzoni at free-electrons.com> wrote:
> > Hello,
> >
> > On Fri,  3 Nov 2017 08:58:56 -0400, Adam Duskett wrote:
> >
> >> +ifeq ($(BR2_PACKAGE_PYTHON3),y)
> >> +REFPOLICY_DEPENDENCIES += host-python3
> >> +REFPOLICY_PYTHON="$(HOST_DIR)/bin/python(PYTHON3_VERSION_MAJOR)"
> >> +else
> >> +REFPOLICY_DEPENDENCIES += host-python
> >> +REFPOLICY_PYTHON="$(HOST_DIR)/bin/python(PYTHON_VERSION_MAJOR)"
> >> +endif
> >
> > I'm not sure why this is needed. Indeed, if BR2_PACKAGE_PYTHON3=y,
> > $(HOST_DIR)/bin/python points to python3, and if
> > BR2_PACKAGE_PYTHON=y, $(HOST_DIR)/bin/python points to python2.
> >
> Huh, didn't know that.  I will change that asap!
>
> > Therefore, you should be able to just use $(HOST_DIR)/bin/python.
> >
> > Could you try that instead?
> >
> > Also, please answer Matt's concerns before sending a v2. Thanks!
> >
> We talked on IRC. :)  The contrib module is included in the tarball as
> Arnout has said.
>
>

Sorry took a bit to get back to this email.  I've figured out what
happened.  Nothing has changed in how refpolicy and refpolicy-contrib
are released.  This patch series changes the package to use a released
archive vs the git repo.  In the upstream git repo it still uses the
submodule for retrieving the contrib repository.  I don't have a good
reason to go either way, but my development approach for refpolicy
leverage's the fact it's a GIT clone (less lines of change in a patch
I maintain on top of buildroot providing selectable GIT repo for this
package).  I could propose this patch if there is interest and that
would clear up which way to go....  we found it was hard to do
refpolicy development purely via patches.


Matt