Poky Project Discussions
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: poky@yoctoproject.org
Subject: [PATCH 0/2] cdrtools recipe cleanup
Date: Mon, 25 Apr 2011 13:08:11 -0700	[thread overview]
Message-ID: <cover.1303761875.git.scott.a.garman@intel.com> (raw)

From: Scott Garman <scott.a.garman@intel.com>

Hi Saul,

Looking closer at the existing cdrtools recipe we have, in fact the
CVE advisory does not apply, since the problematic utility (rscsi)
is staged in ${sbindir} and the custom do_install() function only
packages ${bindir}.

So instead I took the opportunity to do some recipe cleanup, updated
the patches, and added distro tracking information.

Pull URL: git://git.pokylinux.org/poky-contrib.git
  Branch: sgarman/cdrtools-cve
  Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=sgarman/cdrtools-cve

Thanks,
    Scott Garman <scott.a.garman@intel.com>
---


Scott Garman (2):
  cdrtools: recipe and patch cleanup
  distro_tracking_fields.inc: add cdrtools recipe

 .../conf/distro/include/distro_tracking_fields.inc |   11 ++++++++++
 .../cdrtools-native/glibc-conflict-rename.patch    |    8 +++++++
 .../cdrtools/cdrtools-native/no_usr_src.patch      |    7 ++++++
 .../cdrtools/cdrtools-native_2.01.bb               |   21 ++++++++++---------
 4 files changed, 37 insertions(+), 10 deletions(-)



             reply	other threads:[~2011-04-25 20:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-25 20:08 Scott Garman [this message]
2011-04-25 20:08 ` [PATCH 1/2] cdrtools: recipe and patch cleanup Scott Garman
2011-04-26  0:22   ` Saul Wold
2011-04-26  0:24     ` Scott Garman
2011-04-26  0:37       ` Saul Wold
2011-04-25 20:08 ` [PATCH 2/2] distro_tracking_fields.inc: add cdrtools recipe Scott Garman
2011-05-06 22:38 ` [PATCH 0/2] cdrtools recipe cleanup Saul Wold

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=cover.1303761875.git.scott.a.garman@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=poky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox