-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Matthew Woehlke on 11/2/2006 2:23 PM: > Eric Blake wrote: >> And while I'm at it, maybe I will figure out how to name my release >> bash-3.1.3- >> 5, so that the bash patchlevel is included in the cygwin release number. > > I thought that was just a matter of what appears in setup.ini? (But > maybe I am wrong...)
setup.ini uses whatever name I give to the cygwin release tarball, but the g-b-s (generic-build-script), which I still use to generate bash releases, prefers reusing the upstream tarball name when possible. Bash is shipped by the tarball name bash-3.2.tar..., not bash-3.2.<patchlevel>.tar.... So it is just a matter of me tweaking g-b-s to include the patchlevel in the cygwin release. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----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 iD8DBQFFSqHv84KuGfSFAYARAgv5AJ44GvErXn51+mstpZg+MFB32dZMdgCeLEdQ VWsmsKqMeZ6rVoK6zDmL7iQ= =3ipK -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/