# from Eric Wilhelm # on Monday 17 July 2006 02:53 pm: >I'm thinking M::B should bundle even its optional dependencies so it > can ask me if I want the feature and dwiw without me having to > install stuff and then reconfigure it (I'm still not clear on exactly > how the optional features are configured.)
OK, so this has a silly dep/version* work-around just to bootstrap us, then builds an in-situ CBuilder and then uses that to build an xs version.pm. It's at least stupid in a few places. Please show me how to do it better. Also, please show me how to "correctly" install the built dependencies (I just put entries in @INC so we'll be using them for the remainder of the build.) The svk export is in this tarball: http://scratchcomputing.com/tmp/M-B-bundled_demo.tar.gz (You'll need a fresh perl for it to really mean much.) If you just want to know what's going on, read these: http://scratchcomputing.com/tmp/M-B-bundled_log.txt http://scratchcomputing.com/tmp/Build.PL.patch http://scratchcomputing.com/tmp/lib.patch I haven't tried to get the dist and install stuff working. (If I did that, I wouldn't be able to get $someone_else to write recursive build support.) This is just to prove that bundled deps can be built without too much code even if they use Module::Build. --Eric -- Speak softly and carry a big carrot. --------------------------------------------------- http://scratchcomputing.com ---------------------------------------------------
