This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: generic build doubts
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Lapo Luchini <lapo at lapo dot it>
- Cc: cygwin-apps at cygwin dot com
- Date: Tue, 24 Feb 2004 10:04:42 -0500 (EST)
- Subject: Re: generic build doubts
- References: <403B4614.5030506@lapo.it>
- Reply-to: cygwin-apps at cygwin dot com
On Tue, 24 Feb 2004, Lapo Luchini wrote:
> I see no reason to use the new:
> export SIG=0 # set to 1 to turn on signing by default
> This doesn't set a "default", it sets a value.
>
> E.g. also using "SIG=1 script.sh all" (as I always did) I get no
> signature at all, of course.
>
> It seems strange to me that I must change the script to "always sign",
> even if the usual user won't need it and would be probably baffled by
> it... but I like to sign my own release nonetheless ;-)
Umm, yes, you're absolutely right, Lapo. I was too intent on Makefile
syntax, and it didn't occur to me that variables set in a *shell script*
override any values coming in from outside. I'll make the necessary
changes in CVS (for other variables as well, if applicable).
BTW, would it make sense to turn on signing if gpg is installed (unless
it's explicitly turned on or off from outside, of course)?
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton