X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_YG X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: How does setup.exe cope with upgrading of already installed packages if there exist modification in installed files? Date: Wed, 19 Oct 2011 13:08:13 -0400 Lines: 7 Message-ID: <3v0u97tfaga3ngfpacu6khchu3m121i77g@4ax.com> References: <25jt97t858qgm15f1ot2b2m4vgjrq69aqo AT 4ax DOT com> <1319043677 DOT 4668 DOT 13 DOT camel AT YAAKOV04> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 > > To complete the set, package maintainers have to separately include a > > simple preremove script, e.g. > > Actually, cygport handles (2) as well. No further intervention should > be necessary once make_etc_defaults is called. I was hoping you'd say that. New feature in the last year or two? -- 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