From: Thomas Zimmermann <ml@vdm-design.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] imagemagick: convert to BBCLASSEXTEND and new staging
Date: Wed, 24 Mar 2010 08:34:04 +0100 [thread overview]
Message-ID: <201003240834.04740.ml@vdm-design.de> (raw)
In-Reply-To: <b6ebd0a51003231748s293a4020v989b8cdf590ccc4@mail.gmail.com>
Am Mittwoch 24 März 2010 01:48:58 schrieb Chris Larson:
> This should not be necessary. native.bbclass automatically sets deps on
> the -native versions of what's in your DEPENDS. Or was there a specific
> reason behind adding libtool-native and removing tiff?
>
No there was no such a reason, i just copied it from imagemagick-
native_0.6.3.5-10 recipe.
The question is, do we convert 6.3.5-10 to BBCLASSEXTEND too, or do we remove
that recipe, or is there a bug about mixed BBCLASSEXTEND and -native recipes,
that -native recipes are preferred?
next prev parent reply other threads:[~2010-03-24 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 22:34 [PATCH] imagemagick: convert to BBCLASSEXTEND and new staging Thomas Zimmermann
2010-03-24 0:48 ` Chris Larson
2010-03-24 7:34 ` Thomas Zimmermann [this message]
2010-03-24 16:09 ` Chris Larson
2010-03-25 8:54 ` Thomas Zimmermann
2010-03-25 9:14 ` Thomas Zimmermann
2010-03-30 5:26 ` Adrian Alonso
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=201003240834.04740.ml@vdm-design.de \
--to=ml@vdm-design.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.