On Apr 06, Daniel Stender wrote: > I've worked towards this now and prepared two packages, debops containing > the scripts [1] and another one, debops-playbooks [2] containing the > playbooks and the roles.
I was worried for a bit, but it looks like the debops-playbooks package works fairly well... Do you get the 'master' branch of all of the roles, or do you grab the last tagged commit? Some of the roles are not tagged yet. The project is in a transition period at the moment where I clean up some of the roles. How will the debops-playbooks be updated when a new role is added or an existing role is updated? I've had an idea to do something similar to https://wiki.debian.org/AutomaticPackagingTools and create a script that could package Ansible Galaxy roles instead of bundling everything in one huge package. Although apart from DebOps itself I'm not sure if other Galaxy users are writing roles to work together, or separately. I'm switching the project mailing list to a self-hosted one (on DebOps, obviously), at https://lists.debops.org/ (mailing list address would be <debops-us...@lists.debops.org>. Can you change that in the package description, or should I make the changes in the documentation first? The various script templates are an issue for lintian... Not sure what to do about that. As for the documentation of various roles, there's a separate http://docs.debops.org/ page generated by Sphinx, code can be found in https://github.com/debops/docs/ repository. Perhaps a separate debops-docs package could be made using that? Maciej
