Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Message-ID: <99B82AA9708ED0119B55006097125A00363EB5@ifk63.mach.uni-karlsruhe.de>
From: Heribert Dahms <heribert_dahms@icon-gmbh.de>
To: "'DJ Delorie'" <dj@delorie.com>, Jason.Tishler@dothill.com
Cc: cygwin@sourceware.cygnus.com
Subject: RE: How does setup.exe handle duplicate files?
Date: Fri, 9 Jun 2000 23:46:29 +0200
MIME-Version: 1.0
Content-Type: text/plain

Hi DJ,

are there valid reasons to have duplicates in the first place?
This isn't Win* where everything is just dumped to system32!
Are we speaking about installing a single package or multiple?
I consider a given package having duplicates in itself buggy.
My definition of a package is that several of them are distinct,
othogonal sets of files, so there also shouldn't be duplicates
across packages. Am I missing something basic here?

Bye, Heribert (heribert_dahms@icon-gmbh.de)

> -----Original Message-----
> From:	DJ Delorie [SMTP:dj@delorie.com]
> Sent:	Friday, June 09, 2000 18:22
> To:	Jason.Tishler@dothill.com
> Cc:	cygwin@sourceware.cygnus.com
> Subject:	Re: How does setup.exe handle duplicate files?
> 
> 
> > I don't see how this policy guarantees that the correct instance of
> > a duplicate file is always installed.
> 
> It doesn't.  There is no way to know which version is the correct
> version.  It's a problem that hasn't been solved yet.
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com