On 10/03/2015 03:49 PM, Shining wrote:
Hello, I downloaded libdockapp from http://windowmaker.org/dockapps/?download=libdockapp-0.7.0.tar.gz and when I extracted the tarball I found no ./configure there, despite instructions in README say there must one. Then I managed to build one by myself using libtool 2.4.2 and autoconf 2.13. I did not touch anything about the original code so the result is I built fifteen new files: aclocal.m4 autom4te.cache compile config.guess config.sub configure dockapp.pc Makefile.in Makefile.in INSTALL install-sh ltmain.sh Makefile.in missing Makefile.in I guess rules about "Submitting patches" as explained in http://windowmaker.org/dev.php don't fit with this case. So what's better? Should I attach just the new files to this list or should I send a tarball with all the sources or what else?
The tarball linked to from the Window Maker website is a snapshot of what's in the git repository, which shouldn't include auto-generated files like these ones.
Probably the best option would be to include instructions in the README telling users how to generate the configure script.
If you'd like to do this, go ahead and submit a patch. Otherwise, I'll try to get around to it in the near future.
Doug -- To unsubscribe, send mail to [email protected].
