All of lore.kernel.org
 help / color / mirror / Atom feed
From: mulhern <mulhern@gmail.com>
To: yocto@yoctoproject.org, mulhern@yoctoproject.org
Subject: [PATCH 0/2] [meta-security] Cleanup of perl recipes.
Date: Thu,  5 Sep 2013 17:56:05 -0400	[thread overview]
Message-ID: <cover.1378412801.git.mulhern@yoctoproject.org> (raw)

Cleanup of perl recipes for CPAN modules in meta-security layer. One is
renamed, one is removed because a recipe already exists in core.
The following changes since commit 5ec81ec5b117de41ed56eb05df271f103213d7be:

  Bastille: document the current status and usability of the Bastille install. (2013-08-30 15:42:10 -0400)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib mulhern/bug5081
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mulhern/bug5081

mulhern (2):
  libenv-perl: Remove redundant recipe in meta-security layer.
  libcurses-perl: curses-perl renamed to libcurses-perl.

 recipes-security/bastille/bastille_3.2.1.bb        |    2 +-
 .../checksecurity/checksecurity_2.0.14.bb          |    2 +-
 recipes-security/perl/env-perl_1.04.bb             |   25 --------------------
 ...{curses-perl_1.28.bb => libcurses-perl_1.28.bb} |    0
 4 files changed, 2 insertions(+), 27 deletions(-)
 delete mode 100644 recipes-security/perl/env-perl_1.04.bb
 rename recipes-security/perl/{curses-perl_1.28.bb => libcurses-perl_1.28.bb} (100%)

-- 
1.7.10.4



             reply	other threads:[~2013-09-05 21:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 21:56 mulhern [this message]
2013-09-05 21:56 ` [PATCH 1/2] libenv-perl: Remove redundant recipe in meta-security layer mulhern
2013-09-05 21:56 ` [PATCH 2/2] libcurses-perl: curses-perl renamed to libcurses-perl mulhern

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.1378412801.git.mulhern@yoctoproject.org \
    --to=mulhern@gmail.com \
    --cc=mulhern@yoctoproject.org \
    --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.