Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Wed, 5 Sep 2001 19:44:26 -0400 From: Christopher Faylor To: Cygwin-Developers AT Cygwin DOT Com Subject: Re: [Fwd: winsup/mingw libstdc++.a] Message-ID: <20010905194426.A15906@redhat.com> Reply-To: cygwin-developers AT Cygwin DOT Com Mail-Followup-To: Cygwin-Developers AT Cygwin DOT Com References: <3B96ACB0 DOT CB3D2063 AT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B96ACB0.CB3D2063@yahoo.com> User-Agent: Mutt/1.3.21i On Wed, Sep 05, 2001 at 06:52:32PM -0400, Earnie Boyd wrote: >I know why you did this, however, I don't like it. This is not the >place for this file. It should be a separate package controlled by >setup.ini. I'm not quite done yet but I thought that we'd previously agreed to make this part of mingw some day. If we make it a separate package then we'll always be saying "Did you install mingw-gcc-extra?" in the cygwin mailing list. In the mingw world, they just have to download mingw-runtime, gcc, and binutils, right? I'd like to keep the packages the same even if I have to juggle the internals around a little bit. I can add stuff to the mingw distribution more easily than I can to the gcc, so it made sense to me to add this to mingw. If we made this a separate package the package depencency code wouldn't even help in this case since nothing would depend on it. It just wouldn't be installed. cgf