Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <99B82AA9708ED0119B55006097125A00363EB5@ifk63.mach.uni-karlsruhe.de> From: Heribert Dahms To: "'DJ Delorie'" , Jason DOT Tishler AT dothill DOT com Cc: cygwin AT sourceware DOT cygnus DOT com Subject: RE: How does setup.exe handle duplicate files? Date: Fri, 9 Jun 2000 23:46:29 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) 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 AT icon-gmbh DOT de) > -----Original Message----- > From: DJ Delorie [SMTP:dj AT delorie DOT com] > Sent: Friday, June 09, 2000 18:22 > To: Jason DOT Tishler AT dothill DOT com > Cc: cygwin AT sourceware DOT cygnus DOT 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 AT sourceware DOT cygnus DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com