view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

    DuckPAN: bold all prefix lines, NOTE -> NOTICE

    The intention is to have them stand out a bit, so this should help.
    In the old case, it could blend in with the output if the user
    happens to be using a chosen color as their base color, since there
    aren't any obvious prefixes on the standard output. If people run
    with bold all the time, they deserve what they get.

    I dunno why I like NOTICE better, but I somehow do. This means
    expanding the prefix_width.. which might be moot now that we don't
    always prefix. 

  Change: bcb084170e874ceafd29efb96ea081b295cd87c1
  Author: Matt Miller <mwmiller@outlook.com>
  Date : 2014-11-10 13:10:02 +0000

    Server: left-align ProgressBar.

    Already seeing the problems with something which doesn't go through
    the `emit` process. It's still helpful, but it requires extra

Changes  view on Meta::CPAN

    different assets.

    Also, look for new gruny-style filenames which addresses #151. 

  Change: 4d47a015a05188cb7fff5870b27d207574447367
  Author: Matt Miller <mwmiller@outlook.com>
  Date : 2014-11-01 23:18:20 +0000

    Config: clean up path separation.

    This straightens out the directory structure, while also expanding
    the application of path(). 

  Change: 7b3adca8388d60b94fc8508d052851e80d849046
  Author: Matt Miller <mwmiller@outlook.com>
  Date : 2014-11-01 22:51:44 +0000

    Server: clean up output a bit.

    Also:

lib/App/DuckPAN.pm  view on Meta::CPAN

	negativable => 1,
	default     => sub { 1 },
	doc         => 'use color output. turn off with --no-colors',
);

option verbose => (
	is      => 'ro',
	lazy    => 1,
	short   => 'v|debug',
	default => sub { 0 },
	doc     => 'provide expanded output during operation',
);

has duckpan_packages => (
	is => 'ro',
	lazy => 1,
	builder => 1,
);

sub _build_duckpan_packages {
	my $self = shift;