Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 16 Sep 2005 10:26:19 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Dave Korn <dave DOT korn AT artimi DOT com>
cc: cygwin AT cygwin DOT com
Subject: RE: setup: how to handle circular dependencies?
In-Reply-To: <SERRANOaPeda2UexM500000003b@SERRANO.CAM.ARTIMI.COM>
Message-ID: <Pine.GSO.4.63.0509161022470.21521@slinky.cs.nyu.edu>
References: <SERRANOaPeda2UexM500000003b AT SERRANO DOT CAM DOT ARTIMI DOT COM>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Fri, 16 Sep 2005, Dave Korn wrote:
> ----Original Message----
> >From: Gerrit P. Haase
> >Sent: 16 September 2005 14:14
>
> > Hi Setup maintainers,
> >
> > I need some circular dependencies, i.e. gcc-core requires
> > gcc-core-mingw because -mno-cygwin will not work without the mingw
> > version of the gcc runtime. However, the gcc-core-mingw package only
> > includes the runtime which needs gcc-core to be useful.
>
> > Maybe I should include the mingw gcc runtimes in the main gcc
> > packages?
>
> I can't see the use in having them separate if gcc-core-mingw is
> really no use whatsoever on its own. Perhaps someone else can think of
> a reason?
The only use I can see is later on, if setup allows optional dependencies,
someone may be able to save disk space by omitting gcc-core-mingw (and
other gcc-mingw packages) if they never plan to use -mno-cygwin. At the
moment, having a circular dependency is the same as having the two in the
same package -- both will be installed (unless the user goes to great
pains to unselect one).
What I would suggest, however, is placing a stub in the main gcc package
that would produce a meaningful error on -mno-cygwin if *-mingw packages
aren't present, thus making gcc-core independent of gcc-core-mingw. If
gcc-core-mingw is that exact stub, then by all means fold it into
gcc-core.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA
--
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/