On Mon, Jul 31, 2006 at 10:30:36PM -0700, chromatic wrote: > * What's the best way to integrate building this module from the main > Makefile? Should it be part of that process?
That depends. Are any of the standard regression tests going to require this module? > * Where should the built module go, and how can we make that work in a > cross-platform way? Copying the two (for now) necessary files out of > blib/lib appropriately is probably the right answer. I'd say let Module::Build handle the install. The install process can invoke Module::Build if it's to be part of the default install. > * Parrot::Embed uses Module::Build, mostly because I find EU::MM bletcherous > and hateful. Porting it to EU::MM is pretty easy, but I haven't done it > because it needs a custom step before testing to build a PBC file. Leaving > it as it is makes maintaining it a little easier for me, but it makes M::B a > dependency for building Parrot. That may or may not be an issue, depending > on what Bundle::Parrot pulls in. I'll vote for adding M::B to Bundle::Parrot. -J --
pgp3vjEjBIIGO.pgp
Description: PGP signature
