View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 405 | WADF | Core | public | 18 Feb 2012 12:52 | 20 Feb 2012 20:04 |
| Reporter | mrosenquist | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Summary | 405: Allow wadf to have a config option for a program that generate the dep-tags so that checkout can be compared | ||||
| Description | At the moment wadf cannot do anything about extra checkouts as it does not know about them, when reprocessing against dep-tags it would be useful to check against them and see if the checkouts match. dep_tag_generate = deploy-info -y | ||||
| Tags | No tags attached. | ||||
|
|
This sounds useful. I think it actually consists of two parts? 1) an option to allow an external program to generate what it thinks the currently-installed dependencies are 2) compare the output of the program with the dep tags The main challenge I see is that (2) is very sensitive to the format/ordering of the file, although I suppose as long as the same tool is used to generate the dep tags in the first place then it should not be too much of a problem. Also WADF should probably only warn rather than try to fix the differences, do you agree? |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 18 Feb 2012 12:52 | mrosenquist | New Issue | |
| 20 Feb 2012 20:04 | timj | Note Added: 441 |
