From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] package-deb: Ignore circular dependencies
Date: Wed, 9 Mar 2016 14:54:40 -0600 [thread overview]
Message-ID: <56E08D90.1090802@linux.intel.com> (raw)
In-Reply-To: <56E08BEB.1000501@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
On 03/09/2016 02:47 PM, Aníbal Limón wrote:
>
>
> On 03/09/2016 02:33 PM, Burton, Ross wrote:
>> On 9 March 2016 at 18:19, Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com
>>> wrote:
>>
>>> + bb.warn("Package %s rdepends on itself. Ignoring
>>> this dependency" % pkg)
>>>
>>
>> Depending on yourself seems wrong no matter what packaging backend you're
>> using, even if it isn't fatal. Maybe this should be added to the general
>> sanity checks in insane.bbclass?
>
> I agree that this situation could happen in other package management
> backends, i don't now if at insane class level we could access the
> dependency tree of the recipes/packages, i like the idea for more
> general mechanism.
I forget to mention will be good if also handle circular dependencies
between recipe/packages. A time ago i added this support on postinst
scripts in package_{deb,ipk} [1].
[1]
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/lib/oe?id=b2c9e7347acdfd0efe1c3dabb853d609233b61b6
>
> alimon
>
>
>>
>> Ross
>>
>
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-03-09 20:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 18:19 [PATCH] package-deb: Ignore circular dependencies Ricardo Ribalda Delgado
2016-03-09 20:33 ` Burton, Ross
2016-03-09 20:47 ` Aníbal Limón
2016-03-09 20:54 ` Aníbal Limón [this message]
2016-03-09 21:00 ` Ricardo Ribalda Delgado
2016-03-09 21:23 ` Mark Hatle
2016-03-09 21:27 ` Mark Hatle
2016-03-09 21:30 ` Ricardo Ribalda Delgado
2016-03-09 21:47 ` Mark Hatle
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=56E08D90.1090802@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ricardo.ribalda@gmail.com \
--cc=ross.burton@intel.com \
/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