Well, I think it's a good idea to have such tool. And I would recommend add the ticket/spec skeletons of guildhall & Guix, say, pkg-list.scm, for better packaging work.
Maybe we should consider to make it a GNU standard one, if so, we need to add ChangeLog and NEWS. And BUGS/HACKING/THANKS could be optional. But I have a question that most of the time I need build-aux stuffs, I don't know if it's necessary to add to this subcommand. Happy hacking! On Mon, 2015-09-14 at 16:20 -0400, David Thompson wrote: > Hello Guilers, > > Following a conversation on #guile about making it easier to generate > boilerplate for new Guile projects and reduce the need to snarf and/or > monkey type build system configs from other projects, I would like to > throw out an idea for a new guild subcommand: > > guild init foo --license=gpl3+ --author="Lemme Tweakit <le...@gnu.org>" > > This could create the following skeleton files: > > foo/COPYING > foo/README > foo/configure.ac > foo/Makefile.am > foo/pre-inst-env.in > foo/foo.scm > foo/foo/config.scm.in > foo/tests/foo.scm > foo/doc/foo.texi > > These files cover the basic necessities for a good source tree: > License and copyright information, introductory text, build system, > manual, base module, configuration module, test suite, and > pre-installation environment. The exact set of files and their > default contents should be adjusted to fit community best practices. > I modeled this possible skeleton directory on Guix, because Guix is > great. :) > > What do you all think? More importantly, would anyone like to > implement this? > > Happy hacking, >