AFAIK, setup doesn't handle "buildRequires". What I've been doing is to only list runtime dependencies for the binary package in the Requires: line, and then just mention the buildtime requirements in the readme.
e.g. you don't list gcc/binutils in the Requires: line of every package. --Chuck Joshua Daniel Franklin wrote: >>Are you kidding? Cygwin-Man is the COOLEST! >> > > And would make a great mascot! > > >>Truth, Justice, and the American Way, my friend. Truth, Justice, and the >>American Way. >> > > Just think of it this way: instead of just some 'man' now we've got a > 'doc'. Hmmm... I wonder if people are going to think this is a Cygwin > version of DrWatson. > > OK, my last question was pretty obvious, but how about this one: > The -src package here contains perl scripts. Is there any way to have > (just) it 'depend' on perl? Or at least warn people beforehand that > they'll need perl to remake the man pages? > > setup.hint: > > sdesc: "Cygwin-specific man-pages for utilities and functions" > ldesc: "The intro.1 and intro.3 man pages for Cygwin. Also includes > autogenerated, man-formatted versions of the cygwin documentation > available online at > http://cygwin.com/cygwin-ug-net/using-utils.html > and > http://cygwin.com/cygwin-api/cygwin-api.html"; > category: Doc > requires: cygwin man > > http://ns1.iocc.com/~joshua/cygwin/cygwin-doc-1.0-1.tar.bz2 > http://ns1.iocc.com/~joshua/cygwin/cygwin-doc-1.0-1-src.tar.bz2 > > __________________________________________________ > Do You Yahoo!? > Yahoo! Tax Center - online filing with TurboTax > http://taxes.yahoo.com/ >
