Opened 4 years ago
Last modified 3 years ago
#286 assigned defect
mbuild should detect when segments in install directory match components in archives
| Reported by: | Eric Swenson | Owned by: | Gary Dixon |
|---|---|---|---|
| Priority: | minor | Milestone: | No Milestore |
| Component: | Tools | Version: | MR12.7 |
| Keywords: | mbuild | Cc: |
Description
If, in order to fix a compilation bug, you extract a source program from a source archive, fix the bug, and then reinvoke mbuild, it doesn't notice that there exists a segment (modified in this case) in the install directory that matches a component in the source archive. The "compile" request works fine -- and compiles the standalone segment, but the source archive is not updated. The bad source (in the archive) is installed. If you later delete the install directory, the fixes you made are lost.
Recommend that mbuild warn if there exists a standalone segment in the source archive that matches a component in a source (or object) archive.
Change History (3)
comment:1 by , 4 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 3 years ago
This is being removed from consideration for MR12.8. If the problem occurs again, please added a comment describing the full details of its occurrence. They are needed to understand the best way to address these symptoms.
comment:3 by , 3 years ago
| Milestone: | MR12.8 → No Milestore |
|---|
Perhaps the solution should also change compile to ALWAYS compile the source component in the archive being added. Then the compile error would still occur, alerting the user about not having updated the component in the archive. That is another check that could be added (with the recommended check suggested above).