Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: ericblake AT comcast DOT net (Eric Blake) To: Aaron Humphrey , cygwin AT cygwin DOT com Subject: Re: Bash/strtoimax error on setup Date: Mon, 18 Jul 2005 17:22:24 +0000 Message-Id: <071820051722.16563.42DBE550000331CC000040B322007456720A050E040D0C079D0A@comcast.net> X-Authenticated-Sender: ZXJpY2JsYWtlQGNvbWNhc3QubmV0 > > Next time I should try to upgrade cygwin first, but it's a pain in the > current version > of setup.exe because it involves deselecting everything else manually. > (If there's a way > to deselect everything at once, and leave it in a mode where you can > actually select a > program to upgrade, then I'd like to know about it, because it always > seems to put setup > into a mode where you can only reinstall, not upgrade. But anyway...) If cygwin is not being run, then there should be no problem updating cygwin and other apps simultaneously. Preremove scripts run before the old version is uninstalled, so they should not fail. But if you do want separate installations, to be sure that cygwin is working before other packages are upgraded, then yes, you really should do cygwin first (cygwin strives for compatibility in only one direction - older apps should run on newer cygwin; but newer apps that depend on newer cygwin will not run on older cygwin). As to the setup UI issue, when you have the package chooser window, select the Keep radio button, then select just cygwin for the update, and it will leave everything else at the current version even if there are newer versions available. > It was just a symbolic link, actually, but I've lost track of how .exe > magic works with > those, so I might just copy instead. Or reinstall bash, as you suggest. Symbolic links are okay if you only use /bin/sh from cygwin problems. The problem is that Windows won't follow symlinks when executing a program, so the bash postinstall does a copy instead of a symlink to ensure that /bin/sh is usable even from Windows. -- Eric Blake -- 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/