This is the mail archive of the
mailing list for the Cygwin project.
Re: cygport and signatures
- From: Eric Blake <ebb9 at byu dot net>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 30 Jul 2007 06:13:57 -0600
- Subject: Re: cygport and signatures
- References: <46ACCC9F.firstname.lastname@example.org>
-----BEGIN PGP SIGNED MESSAGE-----
According to Steffen Sledz on 7/29/2007 11:21 AM:
> Cygport README mentioned GPG .sig files for all the files used to build
> up a package. As I could see, the prep stage checks these. But they are
> not made part to the final source package in package stage. Is this
> intentionally or a bug?
If you set SIG in your environment (to anything, although 'export SIG=1'
seems simplest), then cygport will automatically prompt for creation of,
and distribute, .sig files as part of the package phase. Cygport 0.2.10
seems to have an issue when trying to unpack a source package that was
built out-of-the-box if SIG is set but .sig files do not exist. Whether
or not you use .sig files is still somewhat optional (I like them, as an
extra layer of assurance, but it is not a requirement for cygwin packages
at the moment).
What usage did you try where things didn't work as expected? Yaakov, as
maintainer of cygport, may be better able to answer whether it was a
cygport bug or a doc bug.
Don't work too hard, make some time for fun as well!
Eric Blake email@example.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----