From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] package-deb: Ignore circular dependencies
Date: Wed, 9 Mar 2016 15:23:44 -0600 [thread overview]
Message-ID: <56E09460.9070105@windriver.com> (raw)
In-Reply-To: <CAJTo0LYeOMKtvdZb2_Nc55Ti+mrbsjFdOEem-mAC+5N5gVt0fQ@mail.gmail.com>
On 3/9/16 2:33 PM, Burton, Ross wrote:
>
> On 9 March 2016 at 18:19, Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com
> <mailto: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?
>
> Ross
>
>
I disagree.. it's quite common for an automatic dependency to trigger a
dependency on one's self. I.e.:
python provides /usr/bin/python
python includes a script that uses /usr/bin/python
depends system now has a provide and dependency for /usr/bin/python in the same
package. This is 'fine'.
Since opkg/deb can't handle file based dependencies, it would be reasonable for
a dependency on /usr/bin/python to be translated to 'python'.
And now you have the python package depending on the python package.
If the package manager interface does not support this, then it should be the
package manager .bbclass that should filter out these items.
This is what we've had to do in the rpm backend... I think it's reasonable for
the deb and opkg backends as well.
--Mark
next prev parent reply other threads:[~2016-03-09 21:23 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
2016-03-09 21:00 ` Ricardo Ribalda Delgado
2016-03-09 21:23 ` Mark Hatle [this message]
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=56E09460.9070105@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@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