From: Diego Elio Pettenò <flameeyes@gm...> - 2011-05-02 17:11:08
I've noticed that the tarballs for ModSecurity are currently prepared
manually, since they tend to vary a lot one between the other.
For common autotools project, the proper way to build the package is
using "make dist"; this does not currently work on ModSecurity because a
number of files are missing.
I suggest, if you want to proceed on that note, that you start by
listing the header files together with the source files in the _SOURCES
variables (even though _HEADERS exists, that's supposed to be used only
for installed ones, all the others are fine with _SOURCES), and the
documentation files into the doc_DATA variable (which also installs
them, which is good).
The idea is for each file that needs to be shipped to be listed
somewhere in the Makefile.am files.
Diego Elio Pettenò — Flameeyes
Get latest updates about Open Source Projects, Conferences and News.