quickly-talk team mailing list archive

[Alistair Buxton <a.j.buxton@xxxxxxxxx>]

On 8 August 2012 18:40, tony byrne <tony.badwolf@xxxxxxxxx> wrote:

> Hi Alistair
>  I reread your proposal and I overlooked "release". Consider a githost
> template whose job is to perform the one line edits required and
> "release". It doesn't contain or import a create command. It doesn't
> contain any project files.
> Put githost.py and release.py in this templates directory.
>
> quickly create ubuntu-application foo
> cd foo
> edit .quickly to rebase the project to your githost template.
> quickly githost (githost.py performs the edits)
> quickly release (release is in the githost template)

Ok, that went completely over my head. Changing the template of an
existing project doesn't sound like a good idea to me? And besides,
the project would still be in a bzr repo locally.

However, after the hangout I realised something: The template system
can really do anything. I could put all the logic to do multiple
hosting services into one template, and then other templates can just
inherit from that one. You still have the problem of exponential
growth in the template library, but it would only affect the default
templates, and not any that I make. Therefore it's not my problem, and
quickly-core doesn't need to worry about it either.


-- 
Alistair Buxton
a.j.buxton@xxxxxxxxx