On Tue, Oct 25, 2005 at 03:59:44PM -0400, Will Coleda wrote: > I think that module is small enough and useful enough for the build > process to include in parrot if we need to (and copying it in is > better than rewriting it from scratch), but... > > I think this would be a good time (esp. after discussion on IRC) to > introduce the possibility of creating a CPAN bundle that is required > for parrot development. This would give us an external dependancy > (con), but it would allow us to remove all the bundled CPAN modules > that we currently have (good), and allow us to easily add or subtract > the required modules as necessary.
I don't think that's necessarily a bad idea but is that really a practical option for things that Configure.pl needs in a non-developmental mode? In this particular case the module would only be needed when the '--maintainer' flag is in use but I imagine that will change in the future as I'd like to tidy up a lot of the probes to use a consistent set of [more rigorous] logic. > We could have a config check early on that checks for the presence of > the required bundled modules and bails, with instructions on how to > grab the Bundle from CPAN and install it. We can tie the required > bundle version to svn revision (or release version, or both) of parrot. That's easily do-able but again I'm not sure that is the right trade-off between ease of building and ease of maintenance. IMHO - since access to CPAN isn't currently a requirement there's nothing wrong with using the Module::Install style of bundling your build time dependencies. If it makes people feel better these could be kept in their own top level directory - perhaps named ./inc? Cheers, -J --
pgpi1OOQtUY5t.pgp
Description: PGP signature
