X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <4F712CFC.9050603@cs.utoronto.ca> Date: Mon, 26 Mar 2012 22:59:08 -0400 From: Ryan Johnson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120312 Thunderbird/11.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] Updated: rebase-4.1.0-1 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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 attention, and the db tells where they can be sent without disturbing the existing dll ecosystem. However, my attempts to do something incremental in /usr/bin have all failed -- because most dlls there are already rebased and several are also in-use -- and I always end up firing up dash in the end. Thoughts? Ryan -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple