On Tue, Aug 01, 2006 at 12:30:28PM -0700, chromatic wrote: > On Tuesday 01 August 2006 12:24, Joshua Hoblitt wrote: > > 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. > > How about when just building Parrot but not installing it? > > I'd also like to run the Parrot::Embed tests as part of the normal Parrot > test > suite.
I'm guessing that Parrot::Embed won't be the last M::B module that were going to stand to ship with Parrot. It would be nice to solve this issue in a somewhat general way so other packages can more or less be mechanically included for use. If not for installation, at least for runtime. While I'd been hoping that M::B had a public method for changing 'blib' this appears not to be the case (just looking at the pod). If this functionality were added we could have the root makefile invoke each module as `perl Build.PL --blib [buildroot/somedir]`, use that path for runtime testing, and still let M::B handle the packages own installation. I admit this scheme is a little hackish but it avoids having to do a custom setup for each bundled package. Thoughts? -J --
pgpd1yK3Vaurb.pgp
Description: PGP signature
