All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OpenEmbedded Devel List
	<openembedded-devel@lists.openembedded.org>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: State of bitbake world, test-dependencies 2015-11-12
Date: Thu, 12 Nov 2015 13:17:21 +0100	[thread overview]
Message-ID: <20151112121721.GE2574@jama> (raw)
In-Reply-To: <CAJTo0LaeSCxpDbt2QmKXyE+hdYJs5Sb7NuVPZ3=1ZzyfrVfd7A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

On Thu, Nov 12, 2015 at 12:12:09PM +0000, Burton, Ross wrote:
> On 12 November 2015 at 11:43, Martin Jansa <martin.jansa@gmail.com> wrote:
> 
> > WARN: clutter-gst-3.0: clutter-gst-3.0 rdepends on libgudev, but it isn't
> > a build dependency?
> > WARN: gammu: gammu rdepends on libgudev, but it isn't a build dependency?
> > WARN: gstreamer1.0-plugins-good: gstreamer1.0-plugins-good-video4linux2
> > rdepends on libgudev, but it isn't a build dependency?
> >
> 
> Looks like oe-core should take gudev for consistency between init systems.

Using correct DEPENDS should be enough to get at least deterministic
builds.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OpenEmbedded Devel List
	<openembedded-devel@lists.openembedded.org>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] State of bitbake world, test-dependencies 2015-11-12
Date: Thu, 12 Nov 2015 13:17:21 +0100	[thread overview]
Message-ID: <20151112121721.GE2574@jama> (raw)
In-Reply-To: <CAJTo0LaeSCxpDbt2QmKXyE+hdYJs5Sb7NuVPZ3=1ZzyfrVfd7A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

On Thu, Nov 12, 2015 at 12:12:09PM +0000, Burton, Ross wrote:
> On 12 November 2015 at 11:43, Martin Jansa <martin.jansa@gmail.com> wrote:
> 
> > WARN: clutter-gst-3.0: clutter-gst-3.0 rdepends on libgudev, but it isn't
> > a build dependency?
> > WARN: gammu: gammu rdepends on libgudev, but it isn't a build dependency?
> > WARN: gstreamer1.0-plugins-good: gstreamer1.0-plugins-good-video4linux2
> > rdepends on libgudev, but it isn't a build dependency?
> >
> 
> Looks like oe-core should take gudev for consistency between init systems.

Using correct DEPENDS should be enough to get at least deterministic
builds.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-11-12 12:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 11:43 State of bitbake world, test-dependencies 2015-11-12 Martin Jansa
2015-11-12 12:12 ` Burton, Ross
2015-11-12 12:12   ` [OE-core] " Burton, Ross
2015-11-12 12:17   ` Martin Jansa [this message]
2015-11-12 12:17     ` Martin Jansa
2015-11-14  9:57 ` Martin Jansa
2015-11-16 15:11   ` Martin Jansa
2015-11-16 16:17     ` Bruce Ashfield
2015-11-16 16:17       ` [OE-core] " Bruce Ashfield

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=20151112121721.GE2574@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --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 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.