Opened 9 years ago
Closed 7 years ago
#1295 closed defect (fixed)
Rasdaman installer error reporting
| Reported by: | Alex Dumitru | Owned by: | Dimitar Misev |
|---|---|---|---|
| Priority: | major | Milestone: | 9.5 |
| Component: | build system | Version: | development |
| Keywords: | Cc: | Peter Baumann | |
| Complexity: | Medium |
Description (last modified by )
The rasdaman installer treats a command string as a command array. The error logger needs to differentiate between the two when printing the command executed.
On failure, the installer should point the user towards the install log file: /tmp/rasdaman_install.$PID.log and should present more information to the user. This has to be researched on how to best do this for commands where a lot of output is being created (e.g. make)
There needs to be a check that /home/$INSTALLATION_USER is writable by $INSTALLATION_USER as git needs to update some things there.
Change History (6)
comment:1 by , 9 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 9 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 9 years ago
comment:4 by , 8 years ago
the installer should also have a —dry-run option perhaps, just logging the commands it plans to do.
comment:5 by , 8 years ago
| Milestone: | 9.2 → Future |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
comment:6 by , 7 years ago
| Milestone: | Future → 9.5 |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
is there any list of files (or at least directories) modified by the installation process?