On 9/21/05, Randy W. Sims <[EMAIL PROTECTED]> wrote: > Shlomi Fish wrote: > > Hi all! > > Hi Shlomi, > > Sorry for the delayed response. >
[ snip ] Spooky. This is *precisely* what I've been trying to figure out today, for a Maypole distribution. > Hmm, MB has some support for creating a custom configuration file. I'm > not sure if the current release is flexible enough to allow what you > want; I haven't really played much with that yet myself. The other > option would be to define a subclass similar to the examples above that > overrides the 'ACTION_code()' method. Call the super class method at the > top, then write out your own module into the blib directory. My understanding is that you can say $builder->config_data( templates_dir => $whatever_tt_inc_returned ); and MB will build and install My::PackageName::ConfigData, which can be loaded and queried for the config setting. My::PackageName::ConfigData contains pod explaining how to use it. d.
