From: Joshua Lock <joshua.g.lock@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/2] pseudo: drop recipe for old 1.6.7 version
Date: Fri, 1 Jul 2016 20:30:32 +0100 [thread overview]
Message-ID: <1467401433-2237-1-git-send-email-joshua.g.lock@intel.com> (raw)
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
---
meta/recipes-devtools/pseudo/pseudo_1.6.7.bb | 19 -------------------
1 file changed, 19 deletions(-)
delete mode 100644 meta/recipes-devtools/pseudo/pseudo_1.6.7.bb
diff --git a/meta/recipes-devtools/pseudo/pseudo_1.6.7.bb b/meta/recipes-devtools/pseudo/pseudo_1.6.7.bb
deleted file mode 100644
index b8c20ad..0000000
--- a/meta/recipes-devtools/pseudo/pseudo_1.6.7.bb
+++ /dev/null
@@ -1,19 +0,0 @@
-require pseudo.inc
-
-SRC_URI = " \
- http://downloads.yoctoproject.org/releases/pseudo/${BPN}-${PV}.tar.bz2 \
- file://fallback-passwd \
- file://fallback-group \
-"
-
-SRC_URI[md5sum] = "4cd39502f9bd0e734dee80e08b28a5f1"
-SRC_URI[sha256sum] = "9f2caca5f1579a376a509cd81a81156fc208650add9f0af275da9e911f18f291"
-
-PSEUDO_EXTRA_OPTS ?= "--enable-force-async --without-passwd-fallback"
-
-do_install_append_class-native () {
- install -d ${D}${sysconfdir}
- # The fallback files should never be modified
- install -m 444 ${WORKDIR}/fallback-passwd ${D}${sysconfdir}/passwd
- install -m 444 ${WORKDIR}/fallback-group ${D}${sysconfdir}/group
-}
--
2.7.4
next reply other threads:[~2016-07-01 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 19:30 Joshua Lock [this message]
2016-07-01 19:30 ` [PATCH 2/2] pseudo: upgrade to 1.8.0 Joshua Lock
2016-07-04 11:36 ` Alexander Kanavin
2016-07-04 12:10 ` Joshua G Lock
2016-07-04 12:14 ` Alexander Kanavin
-- strict thread matches above, loose matches on Subject: below --
2016-07-05 12:18 [PATCH 0/2] Pseudo upgrade Joshua Lock
2016-07-05 12:18 ` [PATCH 1/2] pseudo: drop recipe for old 1.6.7 version Joshua Lock
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=1467401433-2237-1-git-send-email-joshua.g.lock@intel.com \
--to=joshua.g.lock@intel.com \
--cc=openembedded-core@lists.openembedded.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