X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4E9EE65E.2080302@bopp.net> Date: Wed, 19 Oct 2011 10:01:50 -0500 From: Jeremy Bopp User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: How does setup.exe cope with upgrading of already installed packages if there exist modification in installed files? References: <25jt97t858qgm15f1ot2b2m4vgjrq69aqo AT 4ax DOT com> <4fmt971clmundcmk1ib78p23encnbkrhl4 AT 4ax DOT com> In-Reply-To: <4fmt971clmundcmk1ib78p23encnbkrhl4@4ax.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 On 10/19/2011 09:13, Andrew Schulman wrote: >> 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. According to this page, you can change where hgweb looks for templates by editing either /etc/mercurial/hgrc or the .hgrc file in the home directory of the user running hgweb: http://mercurial.selenic.com/wiki/Theming Rather than making a complex postinstall script than can manage overrides sanely, it would be better to copy the packaged template files into a new location outside of the paths managed by the packages and then configure hgweb to look for them in the new location. You'll then be free to make any changes you like then without fear that they will be inadvertently clobbered. -Jeremy -- 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