View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005498 | Taler | deployment and operations | public | 2018-12-06 13:14 | 2019-05-30 23:11 |
| Reporter | Marcello Stanisci | Assigned To | Marcello Stanisci | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | no change required | ||
| Summary | 0005498: Taler builder/installer should be more fine-grained | ||||
| Description | The current installing/building logic does always a full-featured Taler install, meaning that _all_ the components are downloaded/compiled/installed at once. However, there are certains use cases -- like the auditor / exchange -- where NOT all components are needed; so it would be useful to provide those use cases a option that excludes certain components (like say all the Pythons) from being installed. | ||||
| Tags | No tags attached. | ||||
|
|
By looking at the current build-logic (the one based on Makefile(s) + stamp-files), when component X changes it gets recompiled after all its dependencies; hence there is never a "superfluous" build. The misleading thing is that the exchange, for instance, depends on the python bank (for running its bank-lib tests), but it's a *real* dependency. So no change required here. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2018-12-06 13:14 | Marcello Stanisci | New Issue | |
| 2019-05-30 23:11 | Marcello Stanisci | Assigned To | => Marcello Stanisci |
| 2019-05-30 23:11 | Marcello Stanisci | Status | new => closed |
| 2019-05-30 23:11 | Marcello Stanisci | Resolution | open => no change required |
| 2019-05-30 23:11 | Marcello Stanisci | Note Added: 0014470 |
