[Catalyst] modperl 1.3 wierdness

[Toby Corkindale]

On Mon, Apr 21, 2008 at 07:23:44PM +0100, Matt S Trout wrote:
> On Mon, Apr 21, 2008 at 07:09:26PM +1000, Toby Corkindale wrote:
> > The above problem was solved by changing the apache config.
> > Before:
> > <Perl>
> >    use lib qw(/my/home/dir);
> > </Perl>
> > PerlModule My::App
> > 
> > After:
> > <Perl>
> >    use lib qw(/my/home/dir);
> >    use My::App;
> > </Perl>
> 
> Yep. PerlModule will do double-loading, as documented, which Catalyst can't
> handle  (and shouldn't need to).
> 
> I suspect you'd've found changing PerlModule to PerlRequire would have done
> the trick as well, though my MP1's rusty.

As is mine.. I wish we'd move away from it here :(

> > I'm still seeing some problems indicating the Plugin::ConfigLoader isn't,
> > well, loading anything, though. Odd.
> 
> If you didn't make install it and deleted the Makefile.PL, it's not going to.
> 
> Catalyst uses the presence of Makefile.PL to check if it's running in an
> unpacked dist versus running installed; since obviously an unpacked dist
> -must- have a Makefile.PL otherwise it's not a valid dist[0]

Aaah yes, I remember hitting this way back! That magic Makefile-detection..

Unfortunately due to somewhat unusual app deployment tactics here, apps get
"installed" manually, into their own little area, along with their required
perl dependencies, thus losing the Makefile.PL, but also requiring that the
config file lived in the same non-standard location.

(it does kind of make sense..)

> Choose one option :)

Erm, does stripping out ConfigLoader and replacing it with a similarly
operating plugin that knows to look in our company-specific locations count? :)

Thanks for the help!
-Toby