Changeset View
Changeset View
Standalone View
Standalone View
README.GIT
Show First 20 Lines • Show All 41 Lines • ▼ Show 20 Lines | |||||
Please don't use autopoint, libtoolize or autoreconf unless you are | Please don't use autopoint, libtoolize or autoreconf unless you are | ||||
the current maintainer and want to update the standard configuration | the current maintainer and want to update the standard configuration | ||||
files. All those files should be in GIT and only updated manually | files. All those files should be in GIT and only updated manually | ||||
if the maintainer decides that newer versions are required. The | if the maintainer decides that newer versions are required. The | ||||
maintainer should also make sure that the required version of automake | maintainer should also make sure that the required version of automake | ||||
et al. are properly indicated at the top of configure.ac and take care | et al. are properly indicated at the top of configure.ac and take care | ||||
to copy the files and not merely use symlinks. | to copy the files and not merely use symlinks. | ||||
In order to generate coverage information, compile with --enable-gcov. | |||||
You need to install lcov for this. Running "make coverage-html" will | |||||
generate a coverage report in coveragereport/index.html. | |||||
werner: FWIW, Maintaining such files in all packages is a pita. We should either replace that by a… | |||||
kaiAuthorUnsubmitted Not Done Inline ActionsHow about adding it to HACKING in gnupg? kai: How about adding it to HACKING in gnupg? | |||||
wernerUnsubmitted Not Done Inline ActionsActually there is another task. We should move away from the distributed gnupg/doc/HACKING as primary source to the gnupg-doc/web/faq/HACKING.org. (or we even move from faq/ to the new devel/) We can more easily update the web page so that new hackers get the latest info and not those from some distributed tarball. gnupg would then distribute a copy retrieved using the "make distcheck". werner: Actually there is another task. We should move away from the distributed gnupg/doc/HACKING as… |
FWIW, Maintaining such files in all packages is a pita. We should either replace that by a link gnupg.org/devel/something or point to the README.GIT in libgpg-error, which is the dependency of all our packages (except for the very special nPth)