| Summary: | tar-based release archives may include excluded directories | ||
|---|---|---|---|
| Product: | [Technology] RTSC | Reporter: | Dave Russo <d-russo> |
| Component: | Core | Assignee: | Dave Russo <d-russo> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | dfriedland, p-geremia, sascha |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | target:3.23.01 | ||
fixed in r1600 (xdc-y16, xdctools 3.23.01 or above) Verified that --no_recursion is passed in the command line. Not certain what else I can do to verify the fix... xdctools 3.23.05 GA is available from here: http://www.sanb.design.ti.com/tisb_releases/XDCtools/3_23_05_61/ |
There is a bug in how we handle "empty" directories when a release script is used and tar is the archiver: o we intentionally preserve empty directories in releases o when release scripts are provided, we run the archiver (tar or zip) by passing a explicit list of files _and_ empty directories to archive o when we run tar we (mistakenly) do not pass the "--no-recursion" option to tar (which would prevent including everything below the "empty" .../debug/ directory) So, this bug _only_ occurs when a release o contains directories that are empty (except for excluded files) _and_ o when tar is the archiver _and_ o a release script has been specified Possible workarounds include 1. use zip rather than tar for all release archives 2. add a dummy file, say README, to the debug/ directories 3. patch xdctools_3_2*/packages/xdc/bld/rcl.tci: replace " --force-local " with " --force-local --no-recursion "