Openembedded Core Discussions
 help / color / mirror / Atom feed
From: leonardo.sandoval.gonzalez@linux.intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Two new devtool plugins: export and import
Date: Thu, 25 May 2017 14:31:46 -0700	[thread overview]
Message-ID: <cover.1495747168.git.leonardo.sandoval.gonzalez@linux.intel.com> (raw)

From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>

These two plugins can be used to share the devtool workspace between uses.
On the import plugin, the are some limitations with the proposed patche:

  * It cannot not limit what is being imported, thus all exported
    workspace is imported for the moment.

  * It is not smart enough to see if the imported metadata is compatible
    as explained on [1], thus after import, the may be issues when bulding the particular
    recipe, i.e imported bbappend does not has the bb counterpart, etc.

[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=10510#c3

The following changes since commit ef506f58da3a95fba2696df749b2b81f9c118847:

  cve-check-tool: backport a patch to make CVE checking work (2017-05-18 14:01:48 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib lsandov1/devtool-import-export
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=lsandov1/devtool-import-export

Leonardo Sandoval (2):
  export: new plugin to export the devtool workspace
  import: new plugin to import the devtool workspace

 scripts/lib/devtool/export.py | 94 ++++++++++++++++++++++++++++++++++++++++
 scripts/lib/devtool/import.py | 99 +++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 193 insertions(+)
 create mode 100644 scripts/lib/devtool/export.py
 create mode 100644 scripts/lib/devtool/import.py

-- 
2.12.0



             reply	other threads:[~2017-05-25 21:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25 21:31 leonardo.sandoval.gonzalez [this message]
2017-05-25 21:31 ` [PATCH 1/2] export: new plugin to export the devtool workspace leonardo.sandoval.gonzalez
2017-05-29 22:23   ` Paul Eggleton
2017-05-25 21:31 ` [PATCH 2/2] import: new plugin to import " leonardo.sandoval.gonzalez
2017-05-29 22:39   ` Paul Eggleton
2017-06-02 17:12 ` [PATCH v2 0/3] Two new devtool plugins: export and import leonardo.sandoval.gonzalez
2017-06-02 17:12   ` [PATCH v2 1/3] export: new plugin to export the devtool workspace leonardo.sandoval.gonzalez
2017-06-12 13:43     ` Paul Eggleton
2017-06-02 17:13   ` [PATCH v2 2/3] ftools: new function to replace strings inside a text file leonardo.sandoval.gonzalez
2017-06-02 17:13   ` [PATCH v2 3/3] import: new plugin to import the devtool workspace leonardo.sandoval.gonzalez
2017-06-12 14:19     ` Paul Eggleton
2017-06-12 15:27       ` Leonardo Sandoval
2017-06-20 18:30   ` [PATCH v3 0/3] Two new devtool plugins: export and import leonardo.sandoval.gonzalez
2017-06-20 18:30     ` [PATCH v3 1/3] export: new plugin to export the devtool workspace leonardo.sandoval.gonzalez
2017-06-20 18:30     ` [PATCH v3 2/3] devtool: function to replace strings inside a text file leonardo.sandoval.gonzalez
2017-06-20 18:30     ` [PATCH v3 3/3] import: new plugin to import the devtool workspace leonardo.sandoval.gonzalez
2017-06-22  8:48       ` Paul Eggleton
2017-06-29 16:40     ` [PATCH v4 0/4] Two new devtool plugins: export and import leonardo.sandoval.gonzalez
2017-06-29 16:40       ` [PATCH v4 1/4] export: new plugin to export the devtool workspace leonardo.sandoval.gonzalez
2017-06-29 16:40       ` [PATCH v4 2/4] devtool: function to replace strings inside a text file leonardo.sandoval.gonzalez
2017-06-29 16:40       ` [PATCH v4 3/4] standard: append md5 tag only if not already present leonardo.sandoval.gonzalez
2017-06-29 16:40       ` [PATCH v4 4/4] import: new plugin to import the devtool workspace leonardo.sandoval.gonzalez

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=cover.1495747168.git.leonardo.sandoval.gonzalez@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox