HACKING 2.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. These notes intend to help people working on the checked-out sources.
  2. These requirements do not apply when building from a distribution tarball.
  3. * First Git checkout
  4. You can get a copy of the source repository like this:
  5. $ git clone git://git.sv.gnu.org/mcron
  6. $ cd mcron
  7. The next step is to get and check other files needed to build, which are
  8. extracted from other source packages:
  9. $ ./bootstrap
  10. And there you are! Just
  11. $ ./configure
  12. $ make
  13. At this point, there should be no difference between your local copy, and the
  14. Git master copy:
  15. $ git diff
  16. should output no difference.
  17. Enjoy!
  18. * Submitting patches
  19. If you develop a fix or a new feature, please send it to the appropriate
  20. bug-reporting address as reported by the --help option of each program. One
  21. way to do this is to use vc-dwim <http://www.gnu.org/software/vc-dwim/>), as
  22. follows.
  23. Run the command "vc-dwim --help", copy its definition of the
  24. "git-changelog-symlink-init" function into your shell, and then run this
  25. function at the top-level directory of the package.
  26. Edit the (empty) ChangeLog file that this command creates, creating a
  27. properly-formatted entry according to the GNU coding standards
  28. <http://www.gnu.org/prep/standards/html_node/Change-Logs.html>.
  29. Make your changes.
  30. Run the command "vc-dwim" and make sure its output (the diff of all your
  31. changes) looks good.
  32. Run "vc-dwim --commit".
  33. Run the command "git format-patch --stdout -1", and email its output in,
  34. using the output's subject line.
  35. * Updating auxilary scripts
  36. Fetch new versions of the files that are maintained in other GNU
  37. repositories by running "make fetch". In case any file in the
  38. Mcron repository has been updated, commit and re-run the testsuite.
  39. * Code coverage
  40. Assuming 'lcov' is installed, it is possible to check the actual code
  41. coverage achieved by the test suite by running the following commands:
  42. $ make check SCM_LOG_DRIVER_FLAGS="--coverage=yes"
  43. $ genhtml tests/*.info --output-directory out
  44. -----
  45. Copyright © 2002-2017 Free Software Foundation, Inc.
  46. Copyright © 2017, 2018 Mathieu Lirzin <mthl@gnu.org>
  47. This program is free software: you can redistribute it and/or modify
  48. it under the terms of the GNU General Public License as published by
  49. the Free Software Foundation, either version 3 of the License, or
  50. (at your option) any later version.
  51. This program is distributed in the hope that it will be useful,
  52. but WITHOUT ANY WARRANTY; without even the implied warranty of
  53. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  54. GNU General Public License for more details.
  55. You should have received a copy of the GNU General Public License
  56. along with this program. If not, see <http://www.gnu.org/licenses/>.
  57. Local Variables:
  58. mode: outline
  59. fill-column: 78
  60. End: