From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] libdbd-sqlite-perl: New recipe for SQLite DBI interface driver
Date: Fri, 29 Jan 2010 11:27:31 +0100 [thread overview]
Message-ID: <hjud6i$77n$1@ger.gmane.org> (raw)
In-Reply-To: <1264759676-23841-1-git-send-email-michael.lippautz@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 29-01-10 11:07, Michael Lippautz wrote:
> ---
> recipes/perl/libdbd-sqlite-perl_1.29.bb | 29 +++++++++++++++++++++++++++++
> 1 files changed, 29 insertions(+), 0 deletions(-)
> create mode 100644 recipes/perl/libdbd-sqlite-perl_1.29.bb
>
> diff --git a/recipes/perl/libdbd-sqlite-perl_1.29.bb b/recipes/perl/libdbd-sqlite-perl_1.29.bb
> new file mode 100644
> index 0000000..10fe73a
> --- /dev/null
> +++ b/recipes/perl/libdbd-sqlite-perl_1.29.bb
> @@ -0,0 +1,29 @@
> +DESCRIPTION = "PERL database interface driver for the SQLite database."
> +SECTION = "libs"
> +LICENSE = "Artistic|GPL"
> +DEPENDS = "libdbi-perl-native"
> +RDEPENDS = "libdbi-perl \
That should be RDEPENDS_${PN}
We did have a script somewhere to check for things like that, does
anyone know where that went?
And can someone more knowledgable about perl than me push these patches
(after fixups)?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLYrgTMkyGM64RGpERAnOEAJ0cVpWnavLn9ssl3Q6wKYXcPO2W1wCeKGwC
+s4lBh3sMT+RMl7dUgQrplo=
=BZHR
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-01-29 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 10:07 [PATCH] libdbd-sqlite-perl: New recipe for SQLite DBI interface driver Michael Lippautz
2010-01-29 10:27 ` Koen Kooi [this message]
2010-01-29 10:37 ` Michael Lippautz
2010-01-29 14:36 ` Chris Larson
2010-01-29 16:04 ` Koen Kooi
2010-01-29 10:28 ` Holger Hans Peter Freyther
2010-01-29 10:34 ` Michael Lippautz
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='hjud6i$77n$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@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 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.