Thanks, that's a good start. I don't want to manually add a line to a Makefile.am if automake can responsibly do it for me, and given that automake knows if I'm making a tar.gz file, a tar.Z file, a shar file, a zip file, a bz2 file, ... then it can also easily genarate signature rules for those cases.
I think... H -- > --MGYHOYXEY6WxJCY8 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Wed, Jul 16, 2003 at 04:45:09AM -0400, Harlan Stenn wrote: > > I'm trying to find a way to have automake generate Makefiles that will > > automatically generate digital signatures for distributions, and trying to > > figure out a good way to handle it. > > Not quite what you asked, but I just add this to my top-level Makefile.am: > > sign: > gpg --detach-sign $(distdir).tar.gz > md5sum $(distdir).tar.gz | gpg --clearsign > $(distdir).tar.gz.md5sum > > Then you make dist and/or distcheck as normal, and when you're ready > to release, make sign. > > I don't see any particular reason why this is worth including in > automake. It's trivial and will probably vary per project anyway. > > --=20 > .''`. ** Debian GNU/Linux ** | Andrew Suffield > : :' : http://www.debian.org/ | Dept. of Computing, > `. `' | Imperial College, > `- -><- | London, UK > > --MGYHOYXEY6WxJCY8 > Content-Type: application/pgp-signature > Content-Disposition: inline > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.2 (GNU/Linux) > > iD8DBQE/FW2tlpK98RSteX8RAt52AJ9KyzPzBhsWQaC5cLeD5Zu0qOmQRACggcuD > oIfUldUEYbzK2jCNNVgHEMo= > =Sooj > -----END PGP SIGNATURE----- > > --MGYHOYXEY6WxJCY8-- >
