All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Karthik Ramanan <a0393906@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [WILINK R8.5 2/2] wl18xx, bt-firmware: Update to R8.5
Date: Wed, 7 Jan 2015 13:21:12 -0500	[thread overview]
Message-ID: <20150107182112.GD4759@edge> (raw)
In-Reply-To: <54AD2A44.9080607@ti.com>

On Wed, Jan 07, 2015 at 06:14:52PM +0530, Karthik Ramanan wrote:
> On 06-Jan-15 11:33 PM, Denys Dmytriyenko wrote:
> >Karthik,
> >
> >You've dropped version from the filenames of all the WiLink components, but
> >updated PV only in ti-compat-wireless. All other packages will go back to 0.0
> >version due to missing PV. And since that version sorts lower, it won't be
> >installed on top of the old version.
> >
> 
> Denys,
> 
> Yes. This was intended, the decision was taken to drop the version
> names so that the recipes can be maintained in a easier manner.
> Note that PV is not defined in many of these recipes.
> 
> I agree with your comment about the issue arising out of this
> missing PV update but since this issue will not arise from a clean
> build and that we don't have any customer on the dra7xx-evm at the
> moment who is on daisy. Can this be patch be taken in the current
> state?

I'm fine dropping the version portion from the filename, but it has to have it 
in some way. Having recipe_X.Y.Z.bb is equivalent to having PV = "X.Y.Z" 
inside the recipe. So, this patch has to be updated to add PV to all the 
recipes, since the version no longer comes from the filename. Yes, many WiLink 
recipes don't have PV set explicitly, only because it was coming from the 
filename. So, either filename should provide the version or set PV explicitly.

And requiring a clean build to avoid any versioning issues is not a good 
strategy - we do interative builds on a nightly basis. Moreover, upgrade path 
at runtime will become an important matter soon with binary feeds provided to 
developers...

-- 
Denys


      reply	other threads:[~2015-01-07 18:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 13:04 [WILINK R8.5 1/2] packagegroup-*-connectivity: Include iptables package Karthik Ramanan
2015-01-06 13:04 ` [WILINK R8.5 2/2] wl18xx, bt-firmware: Update to R8.5 Karthik Ramanan
2015-01-06 18:03   ` Denys Dmytriyenko
2015-01-07 12:44     ` Karthik Ramanan
2015-01-07 18:21       ` Denys Dmytriyenko [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=20150107182112.GD4759@edge \
    --to=denys@ti.com \
    --cc=a0393906@ti.com \
    --cc=meta-arago@arago-project.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.