Open JonasGroeger opened 7 years ago
@JonasGroeger Folks can choose which they want. We have some folks out there that have quite a few existing packages using Ketarin and it is not an easy transition over to AU. So providing a solution that works for them as well is/was important.
Never heard of cookiecutter. Interesting.
OT: So you are "VeryChocolatey"! That is an interesting username! :)
Cheers :beers: !
I do have to agree cookiecutter is awesome, and I think the best benefit of it might be the ability to quickly create a single package repo or an automatic packages repo simply by passing arguments to the creation instead of cloning this repo and deleting a bunch of stuff you don't want/need. Overall though ferventcoder is right, the maintainer can make the call about how they want to structure their repo, we just point them here if they want to use what the coreteampackages repo is modeled on (eventually it will be fully consistent).
MS Visual Studio integrates cookiecutter templates, pretty awesome :). I was lookingout for one also for chocolatey packages.
Given that Chocolatey CLI has built in support for templates, I don't think this would be required? There is a repository where the community can add templates: https://github.com/chocolatey-community/chocolatey-templates
https://github.com/audreyr/cookiecutter
This would streamline the setup process even more. I personally would also let out the Ketarin stuff.