From: Simon Busch <morphis@gravedo.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] python-pycairo: convert to new style staging and bump PR
Date: Fri, 15 Oct 2010 18:46:23 +0200 [thread overview]
Message-ID: <4CB8855F.4090304@gravedo.de> (raw)
In-Reply-To: <AANLkTi=tvR6=LmMyEjwXQSuDBHJsbMH6dUZrnpBzOMc3@mail.gmail.com>
On 15.10.2010 09:07, Frans Meulenbroeks wrote:
> Some concerns:
> I don't think STAGING_INCDIR should be used; guess it should go to
> ${D}/${includedir} (just like the 1.8.0 version does).
> You might also peek at the do_install_append of the 1.8.0 recipe as it
> does different/more things. I don't know too much about pycairo, but I
> can imagine these make sense for 1.4.0 too.
I even don't know much about pycairo in detail I just noted that it does
not compile in its current state and changed it to new style staging.
But I will check if it makes more sense to change the staging path to
${D}/${includedir} as I just copied what was already there in do_stage().
> Then again perhaps it is time to move to 1.8.0; this version has a
> DEFAULT_PREFERENCE of -1, but angstrom 2008 and 2010 and kaeilos
> already have 1.8.0 as preferred version (and the 1.8.0 version is
> around for 1.5 year or so).
For me it should be ok to drop 1.4.0 and use 1.8.0 if nobody else uses
it. Btw. there is already a newer version of pycairo available. It's
1.8.10 but they changed it's name to py2cairo. pycairo is now the name
for the version with python 3.x support.
> BTW the latest version of cairo is 1.8.10 so we might consider moving
> to that version too.
No, it's not. The latest version of cairo is 1.10.0 :) SHR is already
using this version ...
regards,
morphis
next prev parent reply other threads:[~2010-10-15 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 6:24 [PATCH] python-pycairo: convert to new style staging and bump PR Simon Busch
2010-10-15 7:07 ` Frans Meulenbroeks
2010-10-15 16:46 ` Simon Busch [this message]
2010-10-18 18:39 ` Simon Busch
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=4CB8855F.4090304@gravedo.de \
--to=morphis@gravedo.de \
--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.