[17:36] <aquarius> mhall119, I've tried following dpm's advice in https://lists.launchpad.net/quickly-talk/msg00173.html -- what I did was create ~/quickly-templates, cp -r /usr/share/quickly/templates/ubuntu-application-qtquick ~/quickly-templates, and then create an empty ~/quickly-templates/ubuntu-application-qtquick/license.py and... quickly license in my qtquick quickly project is still failing with an error in
[17:36] <aquarius> /usr/share/quickly/templates/ubuntu-application/license.py .  I'm not sure what I'm supposed to do :(
[17:38] <dpm> aquarius, is quickly looking at ~/quickly-templates at all? (I'm asking because I can't remember if it does by default, or if you have to set up an environment variable to do so). mterry or didrocks might know
[17:39] <aquarius> dpm, I don't know. mhall119 suggested it would. I have also tried QUICKLY_TEMPLATES=/home/aquarius/quickly-templates quickly license and that didn't work either ;)
[17:39] <aquarius> aha, mterry might know. mterry, ping. :)
[17:39] <mhall119> aquarius: the code says it looks there, I'm just not sure where it looks *first*
[17:39]  * aquarius laughs
[17:39] <aquarius> mhall119, so it might be useful for adding brand new templates but not necessarily for overriding
[17:40] <mhall119> you can re-name it to ~/quickly-templates/aq-application-template, then in your .quickly file change the template to aq-application-template
[17:40] <mhall119> aquarius: possibly
[17:41] <dpm> aquarius, or simply uninstall the qt and qtquick templates
[17:41] <dpm> then you're sure it uses those from /home
[17:41] <aquarius> stupid question: quickly doesn't require the templates at runtime, right?
[17:41] <aquarius> they're just used to create the project, which is then standalone?
[17:41] <dpm> I don't think so, no
[17:41] <dpm> yeah
[17:41] <dpm> not a stupid question, btw :)
[17:42] <aquarius> dpm, I was trying to avoid uninstalling the real ones because then I'm basically forking the template :P
[17:42] <aquarius> or creating aq-application-template
[17:42] <dpm> so you're avoiding at all costs to become the maintainer :)
[17:42]  * aquarius laughs
[17:42] <aquarius> essentially, yes :)
[17:42] <aquarius> because I don't have the time to be a good maintainer
[17:43] <aquarius> so if I end up being The Guy, there'll be someone else in my position three months from now and I'll be too busy to help them and they'll be just as frustrated as I am :P
[17:43] <dpm> it'll probably be small fix you're contributing, come on, we'll make sure you don't get commit rights :)
[17:44] <aquarius> haha! I like mhall's trick of renaming the template
[17:45] <aquarius> that works, sorta
[17:45] <aquarius> dpm, it seems that having an empty license.py file in the template root isn't enough to provide a license command. :)
[17:45] <aquarius> mhall119, how do I provide a "quickly license" command in my template?
[17:46] <aquarius> dpm, I should note that doing this rename-the-template trick breaks anyone else who wants to hack on my code, because they don't have a ubuntu-application-qtquick-sil template, but once I've contributed the fix I'll change it back :)
[17:47] <dpm> hahaha, ok
[17:47] <dpm> in any case, essentially, right now the quickly-community-templates are (un)maintained on a best-effort basis, so if you manage to get the template fixed, just send the mp, ping us here, we'll get the fix in and won't beg you to become the maintainer.
[17:48] <dpm> Quick and painless. Well the part of actually implementing the fix _might_ be a bit of a pain :)
[17:48] <aquarius> dpm, there are two ways I could fix this: disable the license command, or fix it to do it right. I'd like to do the second, but I don't know how much work it is yet :P
[17:52] <dpm> :)
[22:25] <aquarius> mhall119, ping aobut DstUtilsExtra and quickly