Description
This would reduce the duplication of code within buildtasks and potentially allow a future evolution of TKLDev to have some common commands/functions that could be leveraged for development work.
Ultimately, it would be best provided as a debian package, but initially probably best contained within buildtasks.
I suggest using a namespace prefix such as tkldev-
or perhaps simply tkl-
or td-
(TurnKey Dev). We could stick with the already established bt-
although, I'm not sure that is a good idea, especially if we scale it out to include other non buildtasks related utilities, or use cases not directly related to buildtasks.
The MVP would probably just include things like:
-
stdout tools such as:
- info
- warning
- fatal
-
apt/dpkg related:
- install
The install function/command could also perhaps include a switch such as --no-update
so that apt-get update
would only need to be run once per script/session (speeding up installs where relevant).
Food for thought. Further discussion more than welcome.