Comment: Patch posted (Score 1) on 2009.06.17 17:55
Attached to: Request for Assistance - The most important toolchain bug
>These "thinkers" get way too far out of touch way too quickly otherwise. "Intuition" is plentiful, cheap, and without the rigors of testing from actual experimentation and application, unfiltered garbage.
Yup.
Working link for the lazy web: http://theworkinggeek.com/2009/06/dirty-presentations-xkcd-and-the-perils-of-14
Just FYI, cpan doesn't seem to like 'install' from the command line:
cpan install Catalyst::Engine::FastCGI
It looks like you specified 'install' as an argument to cpan(1). This
script is not the CPAN.pm prompt and doesn't understand the same commands.
In fact, doesn't require the extra typing. You probably just want to
list the modules you want to install:
cpan Catalyst::Engine::FastCGI
See the documentation for more details on using this script.
Hah, that's interesting
Yes, AFAIK Module::Pluggable doesn't cache its results, to each time you call ->plugins it will rescan the hierarchy
Usually people only load a config at startup once, so it's not typically a problem
In Config::Any:
{ my (@plugins, $loaded); sub plugins { return @plugins if $loaded; $loaded = 1; return @plugins = $finder->plugins } }
http://rt.cpan.org/Public/Bug/Display.html?id=46045
Yes, it has the command-line sugar, but it also needs to be able to complete successfully (I realize this can be problematic with out-of-date installations)
Finally, we need to blat "cpan -i (package)" over the web so people can easily find out how to do it. Maybe even include some pointers to local::lib
Can you be a little bit more specific about how you want CPAN2 to work?
This has been a sore point for me lately, I really think we need to do a better job of lowering the barrier of entry to access CPAN.
For example, if I do some searches for CPAN (on Google), it's difficult to find clear instructions on how to install stuff. The examples I've seen show something like this:
perl -MCPAN -e shell
BEFORE introducing
cpan -i
I mean really, put the newbie into a strange environment? Not a great idea IMHO.
http://sial.org/howto/perl/life-with-cpan/ is really terrific, I mean, a wonderful resource. However, there's no clear synopsis on the top on how to install, say, Moose.
Installing a CPAN module should be as easy as doing
apt-get install (package)
Perl IS CPAN, and we need to make it more accessible to the newish developer.
Right tool for the job
Sometimes procedural is the way to go, there's nothing wrong with that
my $p = Net::Ping->new(); my $alive = $p->ping('127.0.0.1'); ok( $alive, 'testing localhost' ); $p->close;
I noticed you are using a role called 'ResultSource'
Are you using DBIx::Class?
If so, how are you integrating it with Moose? Are you extending the DBIx::Class'es or are you wrapping the storage object (the row)?
That is, do you have two classes for each business entity: one for the model and one for the storage (DBIx::Class)?
How do you store roles in a project (where do they go in your namespace)?
Do you have a special package, like:
MyFramework::Role::Does*