Include buildtasks in TKLDev by default (option for non-ISO builds)

[JedMeister]

As per this thread it'd be great if TKLDev actually included the option to build alternatives build types (e.g. OVZ, LXC, VMDK, etc) rather than just ISOs.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[JedMeister]

Also it'd be nice if you could (optionally) set the default filesystem size (i.e. currently VMDK builds are 20GB).

[JedMeister]

FWIW the OVZ build code (apply to ISO with TKLPatch) is available here (2 patches attached to first post in thread).

The other build code is still outstanding...

[JedMeister]

TKL Devs have released buildtasks. It provides the scripts that build all the other build types.

It is not all that well documented but essentially provides scripts to produce the different builds (from ISO) and should be pretty straightforward (from my quick glance at the code).

As it's not yet integrated into TKLDev I'm leaving this issue open.

[JedMeister]

I have left this pinned to v14.2 milestone for now, but I think we need to discuss this a little more until we can be sure exactly how we want to go with this.

[JedMeister]

@Dude4Linux made a good point in #586 (comment), to paraphrase; buildtasks is more for maintainers.

I think that he's right but it shouldn't be! I might like to produce a "custom" LXC template to run on Proxmox!? Or maybe @jstruebel wants to patch a few appliances with his OpenLDAP patch all in one go, perhaps a couple of appliances need an additional patch at the same time too?! Someone else might want to build some VMs (OVA)?!

Initially we'd just clone it like we do with common I guess? What should we do with the dependencies? I doubt that most users are going to need/want to install all the functionality?! Currently the scripts either fail if dependencies are missing or in the case of Docker and Proxmox they'll install them.

It is our release tool so we'll need to be careful how we do it, but I'm sure we could make it more generically useful to developers while keeping it solid and reliable for us.

Would love some input!