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