10510 2016-10-27 19:10:17 +0000 devtool: add ability to export / import work in progress 2017-08-23 16:33:48 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools 2.2 x86 Multiple RESOLVED FIXED Medium+ enhancement 2.4 M3 11737 1 bluelightning leonardo.sandoval.gonzalez leonardo.sandoval.gonzalez ross.burton --- --- Yes (doc changes required) oldest_to_newest 67661 0 bluelightning 2016-10-27 19:10:17 +0000 Enable basic collaboration by allowing the user to export one, several or all recipes from their workspace to a single file (tarball?) so that they can be imported by someone else also using devtool. Sources should be included in the tarball if they are in the workspace, at least by default. 70129 1 leonardo.sandoval.gonzalez 2017-01-25 16:47:15 +0000 M2 missed. Targeting for current milestone. 70718 2 leonardo.sandoval.gonzalez 2017-02-15 20:28:11 +0000 (In reply to comment #0) > Enable basic collaboration by allowing the user to export one, several or > all recipes from their workspace to a single file (tarball?) so that they > can be imported by someone else also using devtool. Sources should be > included in the tarball if they are in the workspace, at least by default. Paul, for the export: I believe the easiest is to find those files related to a specific recipe or recipes and create a tar based on this for the import: based on the above tar file, just untar it skipping those that workspace files that can be overwrite If this is what you want, I believe devtool export/import plugins would act as a simple tar wrappers. I wait for your comments before proceeding. 71331 3 bluelightning 2017-03-16 03:25:01 +0000 Yes, that's part of it - we also need to ensure that the relevant entries in the .devtool_md5 get exported and imported as well. It also occurs to me that it's possible that user A does an export of a recipe and then user B tries to import that on their system with incompatible metadata - i.e. where the version is different or the recipe is not even available. If we're importing a bbappend, we should check that the bbappend is still applicable (i.e. that a matching recipe exists in the user's configuration) and error out if that's not the case. 73520 4 leonardo.sandoval.gonzalez 2017-05-25 21:36:49 +0000 (In reply to comment #3) > Yes, that's part of it - we also need to ensure that the relevant entries in > the .devtool_md5 get exported and imported as well. > > It also occurs to me that it's possible that user A does an export of a > recipe and then user B tries to import that on their system with > incompatible metadata - i.e. where the version is different or the recipe is > not even available. If we're importing a bbappend, we should check that the > bbappend is still applicable (i.e. that a matching recipe exists in the > user's configuration) and error out if that's not the case. Paul, I realized that this work deserves a separate bug (devtool import being a bit more smart). I will file bug once the following series have been reviewed so direction is clear: http://lists.openembedded.org/pipermail/openembedded-core/2017-May/137140.html 73986 5 leonardo.sandoval.gonzalez 2017-06-12 15:17:15 +0000 Several comments from Paul, requiring a full revision of proposed pluings, so moving it to the next milestone. 74654 6 leonardo.sandoval.gonzalez 2017-06-29 16:53:23 +0000 New series revision sent to review (this is the v4): http://lists.openembedded.org/pipermail/openembedded-core/2017-June/138887.html 75132 7 leonardo.sandoval.gonzalez 2017-07-19 14:53:59 +0000 Patches are in the ML, just did not arrive to master yet. Moving to M3. 76086 8 leonardo.sandoval.gonzalez 2017-08-23 16:33:48 +0000 With some changes from Paul on the proposed patches, finally landed to master. 2de8ba89ef: Leonardo Sandoval: Mon Aug 21 08:30:32 2017 +0100: devtool: import: new plugin to import the devtool workspace f9bc3b5101: Leonardo Sandoval: Mon Aug 21 08:30:32 2017 +0100: devtool: export: new plugin to export the devtool workspace