Hi Pascal, [Re: [yocto] [meta-selinux][PATCH] selinux-userspace: update userspace SRC_URI and checksums] On 14.09.17 (Wed 17:14) Pascal Ouyang wrote:
> 于 14-9-16 上午3:46, Joe MacDonald 写道: > >diff --git a/recipes-security/selinux/selinux_20131030.inc > >b/recipes-security/selinux/selinux_20131030.inc > >index 2cb35d5..01cc52f 100644 > >--- a/recipes-security/selinux/selinux_20131030.inc > >+++ b/recipes-security/selinux/selinux_20131030.inc > >@@ -1,5 +1,5 @@ > > SELINUX_RELEASE = "20131030" > > > >-SRC_URI = > >"http://userspace.selinuxproject.org/releases/${SELINUX_RELEASE}/${BPN}-${PV}.tar.gz"; > >+SRC_URI = > >"https://github.com/SELinuxProject/selinux/archive/${BPN}-${PV}.tar.gz"; > > > Hi Joe, > > I have tested and want to change the SRC_URI to: > https://raw.githubusercontent.com/wiki/SELinuxProject/selinux/files/releases/${SELINUX_RELEASE}/${BPN}-${PV}.tar.gz > so we can get separate tarballs and no checksum changes. I'd already pushed this change by the time you'd sent out this email, but we could revise it if you felt really strongly about it. I don't think that's really necessary though. I knew about the raw.githubusercontent.com link, they're actually the links you get pointed at for the refpolicy releases, which I'm currently updating, but if you follow the 'releases' link on the SELinuxProject github page for 'selinux', you get pointed at the release tarballs I've referenced in my commit. I think in this case it's best to follow the most official sources for the release. This also fits well with the next logical step of using the single release tarball of the official sources: https://github.com/SELinuxProject/selinux/releases which is what I'm planning to do for the userspace update I'm working on now. What do you think? -J. -- -Joe MacDonald. :wq
signature.asc
Description: Digital signature
-- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
