From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Christopher Larson <chris_larson@mentor.com>
Subject: Re: [meta-oe][PATCH 0/3] Add bits to save/restore URI headrevs
Date: Tue, 15 Dec 2015 20:49:39 +0100 [thread overview]
Message-ID: <20151215194939.GE2556@jama> (raw)
In-Reply-To: <cover.1450208019.git.chris_larson@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 2691 bytes --]
On Tue, Dec 15, 2015 at 12:37:44PM -0700, Christopher Larson wrote:
> From: Christopher Larson <chris_larson@mentor.com>
>
> This is useful to support BB_NO_NETWORK with AUTOREV, by letting someone ship
> dumped headrevs to the user, who then inherit this class, which ensures that
> the cached headrevs are used, and upstream is not contacted at parse time.
> BB_SRCREV_POLICY will be set to "cache" as well, if it's not already set, as
> otherwise bitbake will contact upstream to update the cached values.
>
> This is helpful when shipping downloads to someone when there's a desire to
> support both BB_NO_NETWORK and AUTOREV.
>
> The restore_headrevs.bbclass will restore dumped headrevs at config parse time
> (add to INHERIT), and the oe.headrevs python module provides a function one
> can call to dump the headrevs.
Maybe I'm missing something, but what's advantage of shipping something
with AUTOREV which is then used together with BB_NO_NETWORK?
We already have some implementation in bitbake which dumps latest
SRCREVs used by all recipes (including AUTOREV) onces so I would expect
that the release will ship this .inc files with locked revisions and if
the user of such release wants to use BB_NO_NETWORK he will also include
that .inc file with locked revisions.
Is it because it's easier of faster to dump them from the headrefs db
you already ship with release and you don't want to generate .inc from
buildhistory?
Cheers,
>
> The following changes since commit 62bfd1f93f8873611e818c7cc8c13a761d629502:
>
> wireshark: update to version 2.0.0 (2015-11-30 14:39:59 -0500)
>
> are available in the git repository at:
>
> git://github.com/kergoth/meta-openembedded.git headrevs
> https://github.com/kergoth/meta-openembedded/tree/headrevs
>
> Christopher Larson (3):
> oe: add python namespace package
> oe.headrevs: save and restore the bitbake URI headrevs
> restore_headrevs.bbclass: add
>
> meta-oe/classes/restore_headrevs.bbclass | 32 +++++++++++++++++++++++++++
> meta-oe/lib/oe/__init__.py | 2 ++
> meta-oe/lib/oe/headrevs.py | 38 ++++++++++++++++++++++++++++++++
> 3 files changed, 72 insertions(+)
> create mode 100644 meta-oe/classes/restore_headrevs.bbclass
> create mode 100644 meta-oe/lib/oe/__init__.py
> create mode 100644 meta-oe/lib/oe/headrevs.py
>
> --
> 2.2.1
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-12-15 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 19:37 [meta-oe][PATCH 0/3] Add bits to save/restore URI headrevs Christopher Larson
2015-12-15 19:37 ` [meta-oe][PATCH 1/3] oe: add python namespace package Christopher Larson
2015-12-15 19:37 ` [meta-oe][PATCH 2/3] oe.headrevs: save and restore the bitbake URI headrevs Christopher Larson
2015-12-15 19:37 ` [meta-oe][PATCH 3/3] restore_headrevs.bbclass: add Christopher Larson
2015-12-15 19:49 ` Martin Jansa [this message]
2015-12-15 20:40 ` [meta-oe][PATCH 0/3] Add bits to save/restore URI headrevs Christopher Larson
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=20151215194939.GE2556@jama \
--to=martin.jansa@gmail.com \
--cc=chris_larson@mentor.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.