Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: Now that the new setup is here...
Content-Type: text/plain;
	charset="us-ascii"
Date: Wed, 10 Apr 2002 10:05:19 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <FC169E059D1A0442A04C40F86D9BA76008AC93@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>, <cygwin-apps AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3A05QG09928

> Okay, it's been a week -- and nobody seems to have noticed.  That's 
> promising.  So, I'll go out on a limb here, and predict that cgf's 
> massive reorg of the sourceware/cygwin dir structure won't 
> upset setup 
> (no pun intended).  

Urrgh.

> However, it may upset people who are anal 
> about what 
> setup does inside it's own "localdir" playground, and may 
> lead to lots 
> of duplication and unnecessary re-downloads -- which is bound 
> to cause 
> consternation.
> 
> But those are social problems, not technical ones.

And ones I have little sympathy for. Setup is a technical tool, not a
social one. It's not aimed at being the best downloader, only the best
installer. Mirroring that handles directory relocation is a sitecopy
style task...
 
> >>> 2) update bzip2 to the latest release -- which involves the grand 
> >>> library split thing (bzip2 -> bzip2 + libbz2_0).  
> However, the name 
> >>> "libbz2_0" is incompatible with the old setup, and even 
> 'cygcheck -c' 
> >>> gets confused prior to the cygwin-1.3.8 release.
> > 
> > But I didn't do this.
> 
> 
> So, what's the opinion here?  Should we cross the Rubicon?

Go. GO. GO!

Rob