From: Roman I Khimov <roman@khimov.ru>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/3] postfix: convert to BBCLASSEXTEND and new staging for native
Date: Thu, 1 Apr 2010 05:05:23 +0400 [thread overview]
Message-ID: <201004010505.26062.roman@khimov.ru> (raw)
In-Reply-To: <20100331202741.GB21433@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 932 bytes --]
В сообщении от Четверг 01 апреля 2010 00:27:41 автор Khem Raj написал:
> > diff --git a/recipes/postfix/postfix.inc b/recipes/postfix/postfix.inc
> > index 6a5f9bb..5b18cef 100644
> > --- a/recipes/postfix/postfix.inc
> > +++ b/recipes/postfix/postfix.inc
> > @@ -1,5 +1,6 @@
> > SECTION = "console/network"
> > DEPENDS = "virtual/db libpcre postfix-native"
> > +DEPENDS_virtclass-native = "virtual/db-native libpcre-native"
>
> Is this really needed. I thought BBCLASSEXTEND should have converted it for
> you and if you wanted to get rid of postfix-native dependency then why is
> it that native wont need it and target recipe will.
Thought so too, but didn't work for some reason, got dependency loop of
python-native being dependent on python-native.
--
http://roman.khimov.ru
mailto: roman@khimov.ru
gpg --keyserver hkp://subkeys.pgp.net --recv-keys 0xE5E055C3
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2010-04-01 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 18:59 [PATCH 1/3] bitbake.conf: add STAGING_SBINDIR_NATIVE Roman I Khimov
2010-03-31 18:59 ` [PATCH 2/3] postfix: convert to BBCLASSEXTEND and new staging for native Roman I Khimov
2010-03-31 18:59 ` [PATCH 3/3] postfix: add 2.7.0 version Roman I Khimov
2010-03-31 20:28 ` Khem Raj
2010-03-31 20:27 ` [PATCH 2/3] postfix: convert to BBCLASSEXTEND and new staging for native Khem Raj
2010-04-01 1:05 ` Roman I Khimov [this message]
2010-03-31 20:24 ` [PATCH 1/3] bitbake.conf: add STAGING_SBINDIR_NATIVE Khem Raj
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=201004010505.26062.roman@khimov.ru \
--to=roman@khimov.ru \
--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.