982
edits
Talk:Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions
Jump to navigation
Jump to search
Talk:Scripted Compilation on Linux Debian/Ubuntu (view source)
Revision as of 23:33, 28 September 2013
, 28 September 2013→Alternative Coding approaches to implement the features -- Ways to structure the script so it can be easily understood and maintained
| Line 60: | Line 60: | ||
The information needed for the work to be done on each component is similar. We could create a bash associative array for each component with items for each piece of information required: | The information needed for the work to be done on each component is similar. We could create a bash associative array for each component with items for each piece of information required: | ||
* process this component or not | |||
* git, svn, zip or other file url | * git, svn, zip or other file url | ||
* branch and revision information | * branch and revision information | ||
* where to put sources, build and install | * where to put sources, build and install | ||
* which version of fgdata to use | * which version of fgdata to use | ||
* special configuration options | |||
* get original sources Y/N | |||
* update sources Y/N | |||
* configure or reconfigure Y/N | |||
* build Y/N | |||
* install Y/N | |||
Logging | |||
The current log file contains a number of lines written by the script using 2>&1 tee | |||
A different approach would be to re-spawn the script with 2>&1 tee | |||
Another would be to have an additional log files with timestamped log entries indicating what is to be done, what has completed successfully and what exactly failed. | |||
=== Proposed features -- New features of the script that have yet to be implemented === | === Proposed features -- New features of the script that have yet to be implemented === | ||