From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Matthew Stanger <matthew_stanger@trimble.com>
Cc: yocto@yoctoproject.org, Gary Thomas <gary@mlbassoc.com>
Subject: Re: Bumping all packages versions
Date: Tue, 21 Mar 2017 10:37:21 -0600 [thread overview]
Message-ID: <1490114241.3261.173.camel@linux.intel.com> (raw)
In-Reply-To: <CANr77M3w1YZVVaMgm_gQWG0YG3fBEQvT22xg5Lf_upCtyxb7pQ@mail.gmail.com>
have you tried the 'bitbake-layes show-recipes' script? that scripts
list the recipes, layer it belongs and the recipe's PV, unfortunately
not in a single line, but data is there.
Leo
On Mon, 2017-03-20 at 11:35 -0600, Matthew Stanger wrote:
> No.... Thanks I'm a rookie :)
>
> On Mon, Mar 20, 2017 at 11:22 AM, Gary Thomas <gary@mlbassoc.com>
> wrote:
> On 2017-03-20 16:52, Matthew Stanger wrote:
> Hi,
>
> I'm running Yocto 1.7.1 and was wondering if there was
> a simple way to roll/bump all package versions. For
> example in
> every .bb I want to bump PV = $version higher. I'm
> trying to do this as we've designed our headless
> system to update
> using opkg but now we are struggling to find a simple
> way to update package versions, we're trying to stay
> away from
> manually doing it as there is a lot of room for error
> when touching so many packages. First, is there a way
> to brute
> force bump all package versions and 2nd is there a way
> to only bump packages that have changed code (like
> auto git hash
> diff or something) without manually bumping the PV
> version in the .bb? What is the proper way to handle
> you distro's
> versioning at the package level?
>
> Are you using the PR server? That's pretty much what it's
> for.
>
> --
> ------------------------------------------------------------
> Gary Thomas | Consulting for the
> MLB Associates | Embedded world
> ------------------------------------------------------------
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
prev parent reply other threads:[~2017-03-21 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 15:52 Bumping all packages versions Matthew Stanger
2017-03-20 17:22 ` Gary Thomas
2017-03-20 17:35 ` Matthew Stanger
2017-03-21 16:37 ` Leonardo Sandoval [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=1490114241.3261.173.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=gary@mlbassoc.com \
--cc=matthew_stanger@trimble.com \
--cc=yocto@yoctoproject.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.