Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
From: "Herb Martin" <HerbM@learnquick.com>
To: <cygwin@cygwin.com>
Subject: RE: SETUP: In-use files have been replaced
Date: Tue, 18 Oct 2005 18:53:25 -0500
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <43557BB5.265EAD70@dessent.net>
Message-ID: <EIOKYD4-000Z9G-JI@mail2.learnquick.com>
X-Sign-LQC: HerbM@learnquick.com/2005-10-18 18:53:34/<cygwin@cygwin.com>=ghevhcjx

> -----Original Message-----
> From: cygwin-owner@cygwin.com 
> [mailto:cygwin-owner@cygwin.com] On Behalf Of Brian Dessent
> Sent: Tuesday, October 18, 2005 5:48 PM
> To: cygwin@cygwin.com
> Subject: Re: SETUP: In-use files have been replaced
> 
> Herb Martin wrote:
> 
> > Wouldn't we also need to stop all Shells or any other 
> CygWin process?
> 
> Yes, of course.
> 
> > And:  If there are not CygWin processes (services, shells, 
> other apps) 
> > is it considered a bug if Setup cannot complete the update?
> 
> What do you mean "cannot complete the update"?  Setup should 
> always be able to perform the updates, but if files are in 
> use it will have to schedule them to be replaced on the next 
> reboot.  There is nothing it can do about this as it's a 
> restriction of the windows filesystem.

The context of the discussion was in use files requiring
a reboot to complete the update so (obviously) I mean:

Would it be considered a bug if all CygWin services, shells,
and apps are shutdown but a reboot is still required by
Setup?

> > I had to use source to compile a module with different from default 
> > options.
> > 
> > How can that module be installed so that Setup will STOP trying to 
> > replace it?
> 
> Don't use the same location as the packaged version.

Oddly enough, I didn't do that (for accidental reasons)
and suspected that my mistake was in NOT using the download
location.

> > (...and thus not need me to uncheck the item, or ensure it is 
> > unchecked, on each  run of Setup.
> 
> If you replace a packaged file with one of your own, you will 
> almost certainly encounter problems at some later point.  All 
> package management systems work this way, which is why you 
> must use the designated locations (/usr/local, /opt, etc.) or 
> otherwise inform the package system of your desire (for 
> example, debian/apt has
> "diversions".)  You will have the same thing happen on a 
> linux system if you replace a file in /usr/lib with a 
> self-compiled one.

So what is the method to teach Setup that the file
has been updated.

The versions are the same LEVEL/source, but my version
has been specially (switches/settings) make compiled.


--
Herb Martin



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

