Skip to content

Commit

Permalink
Build results of 0125f2f (on master)
Browse files Browse the repository at this point in the history
  • Loading branch information
kentfredric committed Jul 10, 2015
1 parent a51b6a1 commit 215f9f1
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 73 deletions.
1 change: 1 addition & 0 deletions dist.ini
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,7 @@ mantissa = 6
normal_form = numify

[PodWeaver / @Author::KENTNL/PodWeaver]
post_code_replacer = replace_with_blank
replacer = replace_with_comment

[AutoPrereqs / @Author::KENTNL/AutoPrereqs]
Expand Down
1 change: 1 addition & 0 deletions dist.ini.meta
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ srcreadme = pod
-remove = Author::KENTNL::RecommendFixes
-remove = MetaData::BuiltWith
PodWeaver.replacer = replace_with_comment
PodWeaver.post_code_replacer = replace_with_blank

[Munge::Whitespace]
filename = LICENSE
Expand Down
75 changes: 2 additions & 73 deletions lib/Asset/Pack.pm
Original file line number Diff line number Diff line change
Expand Up @@ -294,6 +294,8 @@ sub _pack_metadata {

1;

__END__
=pod
=encoding UTF-8
Expand Down Expand Up @@ -492,76 +494,3 @@ This is free software; you can redistribute it and/or modify it under
the same terms as the Perl 5 programming language system itself.
=cut

__END__
#pod =head1 SYNOPSIS
#pod
#pod #!/usr/bin/env perl
#pod use Asset::Pack;
#pod # lib/MyApp/Asset/FooJS.pm will embed assets/foo.js
#pod write_module('assets/foo.js','MyApp::Asset::FooJS','lib');
#pod # Or better still, this discovers them all and namespaces under MyApp::Asset
#pod find_and_pack('assets', 'MyApp::Asset");
#pod # It also writes MyApp::Asset which is an index file
#pod
#pod =head1 DESCRIPTION
#pod
#pod This module allows you to construct Perl modules containing the content of
#pod arbitrary files, which may then be installed or fat-packed.
#pod
#pod In most cases, this module is not what you want, and you should use a
#pod C<File::ShareDir> based system instead, but C<File::ShareDir> based systems are
#pod inherently not fat-pack friendly.
#pod
#pod However, if you need embedded, single-file applications, aggregating not only
#pod Perl Modules, but templates, JavaScript and CSS, this tool will make some of
#pod your work easier.
#pod
#pod If anything fails it throws an exception. This is meant for scripts that will be tended by
#pod a human (or analyzed if it fails as part of a build).
#pod
#pod =head1 SEE ALSO
#pod
#pod =over 4
#pod
#pod =item * L<< C<App::FatPacker>|App::FatPacker >>
#pod
#pod C<App::FatPacker> is the primary module C<Asset::Pack> is targeted at. C<AssetPack>
#pod creates C<Perl Modules> in a format compatible with C<App::FatPacker> to enable embedding
#pod arbitrary resources in your single-file application.
#pod
#pod =item * L<< C<App::Implode>|App::Implode >>
#pod
#pod C<App::Implode> is like C<App::FatPacker>, except uses L<< C<Carton>|Carton >> and C<cpanfile>'s
#pod to build your app tree. This should be compatible with C<Asset::Pack> and bugs involving it will
#pod certainly be looked into.
#pod
#pod =item * L<< C<App::FatPacker::Simple>|App::FatPacker::Simple >>
#pod
#pod Again, Similar in intent to C<App::FatPacker>, offering a few different features, but
#pod is more manually operated. This module may work in conjunction with it.
#pod
#pod =item * L<< C<Module::FatPack>|Module::FatPack >>
#pod
#pod Similar goals as C<App::FatPacker>, but not quite so well engineered. This code will
#pod probably work with that, but is at this time officially unsupported.
#pod
#pod =item * L<< C<Module::DataPack>|Module::DataPack >>
#pod
#pod This is basically a clone of C<Module::FatPack> except has the blobs stored in your scripts
#pod C<__DATA__> section instead of being a hash of strings.
#pod
#pod Given this module I<also> exploits C<__DATA__>, there may be potential risks involved with this module.
#pod And as such, this is not presently officially supported, nor has it been tested.
#pod
#pod =item * L<< C<Data::Embed>|Data::Embed >>
#pod
#pod C<Data::Embed> is probably more similar than all the rest listed to what C<Asset::Pack> does,
#pod except: it doesn't use built-in C<Perl> mechanics, will probably not be C<FatPacker> friendly, and its
#pod implementation relies on C<Data::Embed> being present to extract embedded data.
#pod
#pod Whereas C<Asset::Pack> is implemented as a simple C<Perl Module> building utility, which generates
#pod independent files which will perform like native C<Perl Module>'s when used.
#pod
#pod =back

0 comments on commit 215f9f1

Please sign in to comment.