On 3/28/2012 15:33, Corinna Vinschen wrote: > On Mar 28 07:27, JonY wrote: >> On 3/27/2012 16:36, Corinna Vinschen wrote: >>> On Mar 26 22:59, Ryan Johnson wrote: >>>> On 26/03/2012 9:40 PM, Jason Tishler wrote: >>>>> New News: >>>>> === ==== >>>>> I have updated the version of rebase to 4.1.0-1. The tarballs should be >>>>> available on a Cygwin mirror near you shortly. >>>>> >>>>> The following are the changes since the previous release: >>>>> >>>>> * Add rebase/rebaseall touch file (i.e., -t option) support. >>>>> >>>>> * Add rebaseall setup (i.e., -p option) support. >>>>> >>>>> * Add .oct to the default rebaseall suffix list. >>>> I've been meaning to ask... but maybe the above-mentioned -p flag >>>> obsoletes it now: What's the most efficient way to rebase after >>>> running setup? We've had the rebase db for a while now, so running >>>> rebaseall seems like overkill. Only the newly downloaded dlls need >>> >>> Now that the new rebase is out, I'm going to create an _autorebase >>> package which will automatically call rebaseall at the end of a >>> successful run of setup, if that run also updated existing DLLs or >>> came with new DLLs. >> >> If I don't want it to run? I've never had any need to rebase DLLs on my >> Win7 64bit machine. > > It doesn't hurt either. > >
I hope it doesn't leave the system in an unusable state if some DLL is still in use. I often have Cygwin processes running when I run setup to add new packages, If any DLLs are in use, upgrade is postponed.
signature.asc
Description: OpenPGP digital signature
