Additional SCM frontends can be supported by Scmbug. Developers and system integrators of the following SCM systems are strongly encouraged to contribute an SCM integration frontend:
Developing a frontend requires:
Committing to support this frontend in future releases of Scmbug.
Creating a new frontend module named src/lib/product/Glue/FrontendName.pm.in. The CVS frontend src/lib/product/Glue/CVS.pm.in serves as a good example.
Updating src/lib/product/Glue/Glue.pm.in:check_configuration accordingly.
Updating the configuration management files configure.in and Makefile.in to autogenerate, and autocleanup the new frontend.
Updating the install-tools rule of Makefile.in to install the new frontend from source.
Creating a new directory named src/glue/templates/frontendname that includes template hook/trigger scripts. The CVS trigger scripts in src/glue/templates/cvs serve as a good example.
Updating src/glue/templates/cvs/*/checkoutlist.in to always extract lib/scmbug/Scmbug/Glue/FrontendName.pm so the CVS SCM frontend does not break.
Updating the Glue Installer src/scripts/install_glue.pl.in and its manpage doc/manpages/install_glue.sgml.1.in to support the new frontend.
Updating the VDD Generator src/scripts/vdd_generator.pl.in and its manpage doc/manpages/vdd_generator.sgml.1.in to support the new frontend.
Updating the Merger src/scripts/merge.pl.in and its manpage doc/manpages/merge.sgml.1.in to support the new frontend.
Updating the documentation in doc/manual/content to reflect support for the new frontend.