At time of release, create ONE commit with all version numbers update in files and named for example "X.X.X".
Create a tag of the name "vX.Y.Z" pointed to that commit and produce releases at that point
-After the release, commit a change to put versions back to MAJOR.MINOR.(PATCH+1)-dev
+To produce release binaries
+ 1) Start from a clean repo and run autogen.sh
+ 2) Configure and 'make dist'
+ 3) Make in cracklib words directory
+ 3) Upload the relevant binaries to a release on github attached to the tag that was already created above
+
+After the release, commit a change to put versions to MAJOR.MINOR.(PATCH+1)-dev
README-LICENSE \
test-data
+DIST_TARGETS=dist-gzip dist-bzip2 dist-zip
+
all-local:
@echo
@echo =======================================================
have available to you - blackhats brute forcing passwords have those
same lists, might as well use it to benefit your security.
+There are HUGE (multi GB) wordlists available online with questionable
+sources, but if you are looking for the most complete source, those
+would be worth investigating.
+
cd ..
autoreconf -f -i
-curl "http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD" > config.guess
-curl "http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD" > config.sub
+curl --silent "http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD" > config.guess
+curl --silent "http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD" > config.sub
#for f in "lt~obsolete.m4" "ltversion.m4" "ltsugar.m4" "ltoptions.m4" "libtool.m4"; do
#curl "http://git.savannah.gnu.org/cgit/libtool.git/plain/m4/${f}?id=v2.4.2.418" > m4/${f}