Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning: mdssdev05.comp.pge.com: esp5 set sender to esp5 AT pge DOT com using -f
Date: Tue, 10 Feb 2004 13:01:39 -0800
From: "Edward S. Peschko" <esp5 AT pge DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cyclical dependencies in setup.ini?
Message-ID: <20040210210139.GA366@mdssdev05.comp.pge.com>
References: <20040210032015 DOT GA146 AT mdssdev05 DOT comp DOT pge DOT com> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040209225210 DOT 0390e8e0 AT 127 DOT 0 DOT 0 DOT 1> <20040210044053 DOT GA210 AT mdssdev05 DOT comp DOT pge DOT com> <20040210050421 DOT GB5893 AT redhat DOT com> <20040210054159 DOT GA270 AT mdssdev05 DOT comp DOT pge DOT com> <20040210060658 DOT GA9177 AT redhat DOT com> <20040210062638 DOT GA315 AT mdssdev05 DOT comp DOT pge DOT com> <Pine DOT GSO DOT 4 DOT 56 DOT 0402100938540 DOT 19284 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.56.0402100938540.19284@slinky.cs.nyu.edu>
User-Agent: Mutt/1.4.1i
X-IsSubscribed: yes

> > well, I need to know which ones to *build* first, and which order
> > to build them.. Like I said I want to do it with as few deps as possible,
> > if possible just g++ and make, and shell.
> 
> I believe I mentioned this before, but anyway...  Most maintainers put the
> build requirements in the Cygwin-specific READMEs in their packages.

what you said was that it was based inside 'configure', ie: if you run configure
that configure would tell you what you need. READMEs are much better.

> One thing that *would*, IMO, be useful is getting access to
> Cygwin-specific package READMEs from the package listing pages.  CGF,
> would keeping the READMEs on the server, even compressed, be a nuisance?
> If not, the script that generates package contents could be modified to
> include a link to the README...

yes you could do that - you could also mandate that the README include build
dependencies in a specific format, and then include these dependencies inside 
of setup.ini as a metadata tag.. 

Ed

--
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/