From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH V4] rrdtool: enable perl and python bindings
Date: Fri, 25 Apr 2014 03:33:26 +0200 [thread overview]
Message-ID: <20140425013326.GR2486@jama> (raw)
In-Reply-To: <5359B8A8.7010801@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]
On Fri, Apr 25, 2014 at 09:21:44AM +0800, Chong Lu wrote:
>
> On 04/24/2014 05:51 PM, Koen Kooi wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Chong Lu schreef op 24-04-14 09:14:
> >> 1. default enable perl and python bindings 2. rrdtool uses perl.real,
> >> perl.real doesn't know where the PERL5LIB should be when prebuilts are
> >> used. Use the wrapper perl instead, perl sets PERL5LIB and invokes
> >> perl.real 3. While using dash as /bin/sh, subsequent commands in
> >> functions will not use the environment variables passed to the function
> >> call line unless explicitly run "export ENV_VAR". 4. delete unrecognized
> >> options: "--enable-local-libpng" and "--enable-local-zlib"
> >>
> >> Signed-off-by: Chong Lu <Chong.Lu@windriver.com> ---
> >> +DESCRIPTION_${PN}-perl = \ +"The ${PN}-perl package includes RRDtool
> >> bindings for perl." +FILES_${PN}-perl =
> >> "${libdir}/perl/vendor_perl/*/*.pm ${datadir}/${PN}/examples \ +
> >> ${libdir}/perl/vendor_perl/*/auto/RRDs/RRDs.*" +RDEPENDS_${PN}-perl =
> >> "perl perl-module-lib perl-module-getopt-long perl-module-time-hires \ +
> >> perl-module-io-file perl-module-ipc-open2 perl-module-io-socket"
> >> +RPROVIDES_${PN} += "${PN}-perl"
> > Why do you need RPROVIDES?
> >
> >
> >> + +DESCRIPTION_${PN}-python = \ +"The ${PN}-python package includes
> >> RRDtool bindings for python." +FILES_${PN}-python =
> >> "${libdir}/python${PYTHON_BASEVERSION}/site-packages/*"
> >> +RDEPENDS_${PN}-python = "python" +RPROVIDES_${PN} += "${PN}-python"
> > Why do you need RPROVIDES?
> If I put rrdtool-python into image.
> I got following errors when I built image.
> Nothing RPROVIDES 'rrdtool-python'
> So, I added RPROVIDES.
Doesn't it make things even worse? It can happily install "rrdtool"
package as "rrdtool-python" provider which is not what one would expect
after adding rrdtool-python to image.
You need to add rrdtool-python rrdtool-perl to PACKAGES.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2014-04-25 1:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 7:14 [PATCH V4] rrdtool: enable perl and python bindings Chong Lu
2014-04-24 9:51 ` Koen Kooi
2014-04-25 1:21 ` Chong Lu
2014-04-25 1:33 ` Martin Jansa [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=20140425013326.GR2486@jama \
--to=martin.jansa@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox