Re: How does setup.exe cope with upgrading of already installed packages if there exist modification in installed files?

2011-10-22 Thread Yaakov (Cygwin/X)
On Wed, 2011-10-19 at 13:08 -0400, Andrew Schulman wrote: 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

How does setup.exe cope with upgrading of already installed packages if there exist modification in installed files?

2011-10-19 Thread Oleksandr Gavenko
How does setup.exe cope with upgrading of already installed packages if there exist modification in installed files? I customize HG templates under: /lib/python2.6/site-packages/mercurial/templates/gitweb/* and would like preserve it when update happen. And it will be good to be notified if

Re: How does setup.exe cope with upgrading of already installed packages if there exist modification in installed files?

2011-10-19 Thread Andrew Schulman
Also I worry about modification in other config files in /etc (like /etc/apache2/httpd.conf). Are they overwritten on package update? This is up to each package maintainer. Current best practice - at least, as of a year or two ago when I asked about it on cygwin-apps I think - is to include:

Re: How does setup.exe cope with upgrading of already installed packages if there exist modification in installed files?

2011-10-19 Thread Oleksandr Gavenko
19.10.2011 16:27, Andrew Schulman пишет: Also I worry about modification in other config files in /etc (like /etc/apache2/httpd.conf). Are they overwritten on package update? This is up to each package maintainer. Current best practice - at least, as of a year or two ago when I asked about it

Re: How does setup.exe cope with upgrading of already installed packages if there exist modification in installed files?

2011-10-19 Thread Andrew Schulman
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

Re: How does setup.exe cope with upgrading of already installed packages if there exist modification in installed files?

2011-10-19 Thread Jeremy Bopp
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

Re: How does setup.exe cope with upgrading of already installed packages if there exist modification in installed files?

2011-10-19 Thread Yaakov (Cygwin/X)
On Wed, 2011-10-19 at 09:27 -0400, Andrew Schulman wrote: This is up to each package maintainer. Current best practice - at least, as of a year or two ago when I asked about it on cygwin-apps I think - is to include: (1) a default config file in /etc/defaults/etc; (2) a preremove script

Re: How does setup.exe cope with upgrading of already installed packages if there exist modification in installed files?

2011-10-19 Thread Andrew Schulman
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? --