All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v2 2/2] usb-modeswitch: Upgrade to latest version
Date: Thu, 10 Jul 2014 15:57:48 +0200	[thread overview]
Message-ID: <20140710135748.GB2433@jama> (raw)
In-Reply-To: <1404998180.9749.53.camel@jrissane-mobl.ger.corp.intel.com>

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

On Thu, Jul 10, 2014 at 04:16:20PM +0300, Jukka Rissanen wrote:
> On to, 2014-07-10 at 14:06 +0200, Martin Jansa wrote:
> > On Thu, Jul 10, 2014 at 02:09:35PM +0300, Jukka Rissanen wrote:
> > > Use the latest version of usb-modeswitch (2.2.0) and
> > > usb-modeswitch-data (20140529). The data package depends
> > > on new usb-modeswitch version so upgrade both of them at
> > > the same time.
> > > 
> > >  
> > > -RDEPENDS_${PN} = "usb-modeswitch"
> > > +RDEPENDS_${PN} = "usb-modeswitch (>= 2.2.0)"
> > 
> > Do we really need the version here?
> > 
> > If yes then add comment explaining why.
> 
> 
> Hmm, I thought the commit message already states that. Do you want that
> also in the recipe itself?

I read it as explanation why you're upgrading 2 recipes in the same
commit, but it doesn't say why you need explicit version in
RDEPENDS_${PN} (instead of letting bitbake do it automatically).

Cheers,

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

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

      reply	other threads:[~2014-07-10 13:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10 11:09 [meta-oe][PATCH v2 1/2] usb-modeswitch: Do not try to use autotools Jukka Rissanen
2014-07-10 11:09 ` [meta-oe][PATCH v2 2/2] usb-modeswitch: Upgrade to latest version Jukka Rissanen
2014-07-10 12:06   ` Martin Jansa
2014-07-10 13:16     ` Jukka Rissanen
2014-07-10 13:57       ` Martin Jansa [this message]

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=20140710135748.GB2433@jama \
    --to=martin.jansa@gmail.com \
    --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.