user-pic

Jeffrey Ryan Thalhammer

  • Commented on Writing version of dependencies
    If you're going to ship your module to CPAN, that might not be the best idea. Setting the minimum version to whatever is installed on your machine might force downstream users to upgrade things unnecessarily. It makes your life as...
  • Commented on DBIx::Class::Schema::Critic and parameterized roles
    Very clever! Coincidentally, I'm starting a fresh project with DBIx::Class, so I can't wait to try the Schema::Critic. I've been thinking about porting Perl::Critic to Moose (or Moo or Mouse), so I'm very curious to look at your implementation. -Jeff...
  • Commented on releasing to [remote] minicpan (preferably with Dist::Zilla)
    I've setup the same kind of system, and it all works just as you've described. But there seems to be a major limitation: it only allows you to inject one module per distribution. Most non-trivial distributions will contain several modules....
  • Commented on First steps with App::Mist
    One suggestion: In your shebang lines, let the user decide which perl to use. Like this: #!/usr/bin/env perl...
  • Commented on First steps with App::Mist
    Hi there- I'm researching a project to provide "A Private CPAN in a box". So I recently started this thread on the perl-qa list: http://www.nntp.perl.org/group/perl.qa/2011/05/msg12747.html Then a colleague suggested I look at App::Mist. It appears there is a lot of...
Subscribe to feed Recent Actions from Jeffrey Ryan Thalhammer

  • brian d foy commented on Writing version of dependencies

    I flip flop on this. For awhile I did it your current way, but I got more complaints that way. Now I only set the minimum version if I know that I must have at least that version for a feature or bug fix.

    I wish we had a way to have an undef version to mean that I don't know what it should be or I'm not specifying it.

  • Tom Wyant commented on Writing version of dependencies

    I've been back and forth on this. Currently I specify whatever I use. That is to say if I use Foo; I specify dependency Foo => 0. If I use Foo 1.2; I specify Foo => 1.2. The use of a version is driven by bug fixes, features, and user feedback.

    But I typically specify core dependencies as well. It is rare for modules to be dropped from core, but it is not unknown.

  • Steven Haryanto commented on Writing version of dependencies
    But I typically specify core dependencies as well. It is rare for modules to be dropped from core, but it is not unknown.

    Not so rare. Looking at perlXXXdelta PODs, modules are routinely being removed from core :) But 'corelist' can help you decide, for example:

    $ corelist attrs
    
    

    attrs was first released with perl 5.00405 and removed from v5.11.0

    But perhaps consider avoiding such modules anyway.

  • Aristotle commented on Writing version of dependencies

    Once upon a time many years ago, declaring dependencies on core modules was problematic because CPAN.pm had a bug and might try to upgrade your perl. But that was then; the bug has been fixed roughly forever. You should never not declare a dependency, even if it is on a core module.

  • Steven Haryanto commented on Writing version of dependencies

    After almost a year, turned out that my habit hasn't changed for the most part. I still write 'Foo=0' and only specify version on rare occasions. I guess laziness FTW!

Subscribe to feed Responses to Comments from Jeffrey Ryan Thalhammer

About blogs.perl.org

blogs.perl.org is a common blogging platform for the Perl community. Written in Perl with a graphic design donated by Six Apart, Ltd.