On Sun, Jul 23, 2017 at 11:37 AM, Thorsten Schöning <[email protected]> wrote: > Guten Tag Robert Middleton, > am Samstag, 22. Juli 2017 um 23:44 schrieben Sie: > >> I tried to verify with: gpg --verify apache-log4cxx-0.11.0.tar.gz.asc >> apache-log4cxx-0.11.0.tar.gz >> but gpg couldn't find the public key - do I need to import a special key at >> all? > > That depends on GPG I guess, is it e.g. checking any public key > servers and if so, which when? Because like the docs told me, In > uploaded my public key to some MIT key server. Additionally, the key > should be available in the KEYS file of the distribution archive. That > would need to be imported manually. >
I will have to check that then, I'm not all that familar with how GPG works with the keys. >> There's no configure script in the archives - for autotools projects, it's >> assumed that they ship with a configure script. > > Isn't that platform dependant and unnecessarily blows the archive? I > removed it by purpose, because "autogen.sh" is creating it and the > docs tell people to use that script. Was needed for source builds > before already and I wondered why we don't simply always require it. > > https://logging.apache.org/log4cxx/next_stable/building/autotools.html > This may help a little: https://www.gnu.org/software/automake/manual/html_node/Basics-of-Distribution.html As far as I'm aware, the configure.sh is not platform-dependent, as it configures the package at that time, checking for platform-specific things(if a header file exists, size of types, etc). The only time you should have to run autogen.sh is to create ./configure in the first place, e.g. when you are building from Git/SVN source, not from the release tarball. Just for reference as well, if you look at the APR source in Git, you'll see that there's no configure script: https://github.com/apache/apr But when you download the release, it has the configure script in it already: http://apr.apache.org/download.cgi -Robert Middleton
