X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_05,RP_MATCHES_RCVD,SPF_HELO_PASS 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 10:13:25 -0400 Lines: 20 Message-ID: <4fmt971clmundcmk1ib78p23encnbkrhl4@4ax.com> References: <25jt97t858qgm15f1ot2b2m4vgjrq69aqo AT 4ax DOT com> 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 > How about templates? > > For example if package like Mercurial provide > WEB templates which I like to customize (fix time format to ISO-8601). > Templates lies in /lib/python2.6/site-packages/mercurial/templates/*. It seems that that's something you'll have to work out with the Mercurial package maintainer. A postinstall script can certainly check to see if templates have changed, and if they have either leave them in place, or even merge in new changes, if you can work out a good way to do that without prompting the user. > If I prepare some fixes to package which list appropriate to write > report to? This is the right list. If you put mercurial in the subject, the maintainer will probably see it. Good luck, Andrew. -- 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