linux/poky.git/scripts/oe-publish-sdk, branch 2.4_M2

oe-publish-sdk: add pyshtables.py to .gitignore

2017-01-31T14:43:00+00:00

pyshtables.py should be ignored by git as it is generated. If kept in the repo, causes subsequent runs of sdk-update to fail. [ YOCTO #10963 ] (From OE-Core rev: 0ac1387bd12b5d023dea06ffe65d1fdcb050bcb4) Signed-off-by: Andrea Galbusera Signed-off-by: Richard Purdie

scripts: python3: change python to python3 in shebang

2016-06-03T12:13:29+00:00

(From OE-Core rev: 4b544ff388497cac82b0585f237900595523e1cb) Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie

devtool: sdk-update: reset git metadata on update

2016-04-18T15:28:22+00:00

Replace git pull with fetch and reset to avoid the merge logic in the event that the layers repo in the published SDK we're updating to isn't fast-forward merge from the local repo. Also add gitignore and committer info during publish to avoid errors and to be sure that the first commit has a dummy user in it. [ YOCTO #9368 ] (From OE-Core rev: 4657bc9d165e51981e034e73e7b92552e873eef7) Signed-off-by: Stephano Cetola Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oe-publish-sdk: exclude sstate-cache if publishing minimal SDK

2016-03-31T22:01:37+00:00

If SDK_EXT_TYPE is set to "minimal" then the SDK won't contain many sstate artifacts, and you're required to set up an sstate mirror in this case anyway so there's no point publishing the "stub" sstate-cache directory from within the SDK since it won't be useful for update purposes and may be confused with the real sstate-cache. There is however a possibility that people might publish the real sstate-cache directory under the same output directory provided to oe-publish-sdk, thus deleting it after extracting (as we were doing with other files we wanted to clean up at the end) would be problematic, besides which extracting it and then deleting it is wasteful. Thus, introduce a "-p" command line option to the SDK installer that we can use to tell tar not to extract the items we don't want when publishing. This has the added benefit of mostly keeping references to these in the place they belong i.e. in populate_sdk_ext.bbclass. (From OE-Core rev: 774b85d42db1d81936d4e4af4f6fb2c57cb51d2c) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

oe-publish-sdk: prevent specifying a directory for the SDK argument

2016-03-31T22:01:37+00:00

The SDK argument is expected to be an installer .sh file; if a directory is specified we can get an ugly failure later on; best to check up front. Fixes [YOCTO #9065]. (From OE-Core rev: ce71f5c2fb8a7b473988da30bbb9bec95e8a6f5e) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

scripts, lib: Don't limit traceback lengths to arbitrary values

2016-03-31T22:01:36+00:00

There appears to have been a lot of copy and pasting of the code which prints tracebacks upon failure and limits the stack trace to 5 entries. This obscures the real error and is very confusing to the user it look me an age to work out why some tracebacks weren't useful. This patch removes the limit, making tracebacks much more useful for debugging. [YOCTO #9230] (From OE-Core rev: 6069175e9bb97ace100bb5e99b6104d33163a3a2) Signed-off-by: Richard Purdie

oe-publish-sdk: fix remote publishing

2016-03-25T10:29:14+00:00

A typo in the command prevented the last part of the publish from succeeding. (From OE-Core rev: 5d51bd1f02fb20e02d0de0ac9874d7f9a6f5ddc6) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

oe-publish-sdk: improve help output slightly

2016-03-25T10:29:13+00:00

This was just copy-and-pasted from devtool - set a reasonable description and tweak the sdk parameter help text. Also add a copyright statement and drop the opening comment describing the command-line syntax that duplicated the help output (with at least one mistake in it). (From OE-Core rev: b18f9cb62e12d068fb840fd7ab9f35b4f039e649) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

oe-publish-sdk: drop SDK installer file from published output

2016-03-25T10:29:13+00:00

We don't really need the SDK installer in the published output, for two reasons: 1) The directory produced is for the consumption of devtool sdk-update, and the installer isn't used by that at all 2) It wouldn't really make sense to point users at the update directory to download the SDK installer because it contains a bunch of things that aren't meant for manual download, so it wouldn't be very tidy. Leaving the file present can mislead you into thinking the opposite of both of the above. (From OE-Core rev: a9ec72b7897ffc0b901c1ccbcbe3cabbc7ac41ee) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

scripts/oe-publish-sdk: add missing call to git update-server-info

2016-01-11T15:41:45+00:00

We need to call git update-server-info here on the created repository or we can't share it over plain http as we need to be able to for the update process to function as currently implemented. (From OE-Core rev: 3ab40bf9d5f19d91e45f7bae77f037b2544e889b) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie