Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Authentication-Warning: mdssdev05.comp.pge.com: esp5 set sender to esp5@pge.com using -f Date: Tue, 10 Feb 2004 13:01:39 -0800 From: "Edward S. Peschko" To: cygwin@cygwin.com Subject: Re: cyclical dependencies in setup.ini? Message-ID: <20040210210139.GA366@mdssdev05.comp.pge.com> References: <20040210032015.GA146@mdssdev05.comp.pge.com> <6.0.1.1.0.20040209225210.0390e8e0@127.0.0.1> <20040210044053.GA210@mdssdev05.comp.pge.com> <20040210050421.GB5893@redhat.com> <20040210054159.GA270@mdssdev05.comp.pge.com> <20040210060658.GA9177@redhat.com> <20040210062638.GA315@mdssdev05.comp.pge.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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/