All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe MacDonald <joe@deserted.net>
To: Pascal Ouyang <xin.ouyang@windriver.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-selinux][PATCH] selinux-userspace: update userspace SRC_URI and checksums
Date: Wed, 17 Sep 2014 09:09:22 -0400	[thread overview]
Message-ID: <20140917130922.GB7912@deserted.net> (raw)
In-Reply-To: <541950EF.2070100@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]

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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      reply	other threads:[~2014-09-17 13:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 19:46 [meta-selinux][PATCH] selinux-userspace: update userspace SRC_URI and checksums Joe MacDonald
2014-09-17  9:14 ` Pascal Ouyang
2014-09-17 13:09   ` Joe MacDonald [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=20140917130922.GB7912@deserted.net \
    --to=joe@deserted.net \
    --cc=xin.ouyang@windriver.com \
    --cc=yocto@yoctoproject.org \
    /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.