On Thu, Jul 17, 2008 at 8:33 AM, Reini Urban <[EMAIL PROTECTED]> wrote: > 2008/7/16 Will Coleda <[EMAIL PROTECTED]>:
>> This looks good; I'd ask you double check which deps are required vs. >> optional: I'm pretty sure we don't -require- any of those packages. >> Ditto for their correspond build deps. (e.g. libgdbm-devel) > > Note, there are more cygwin-side updates to come to this README, > which I will commit after my parrot-0.6.4 release (in 1-2 days). > > In which pod should we document the non-windows package requirements? > Most of those packages have similar names anyway for every unix/posix > platform. > >> parrot is recursively listed as a build requirement > > oops. > >> For the optional items, perl's Moose should be on the list (for >> smartlink), and Test::Perl::Critic/Perl::Critic for the critic tests. >> (Honestly we should have this documented somewhere else and just refer >> to it from here.) > > Good. Where? How about docs/dependencies.pod (new file)? This can house the optional systems we probe for, and a list of the non-core perl modules we're using (and what they're used for.) Thanks for the work on cygwin! -- Will "Coke" Coleda
