Hello community,

here is the log from the commit of package perl-Mojolicious-Plugin-AssetPack 
for openSUSE:Factory checked in at 2017-05-27 13:19:08
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/perl-Mojolicious-Plugin-AssetPack (Old)
 and      /work/SRC/openSUSE:Factory/.perl-Mojolicious-Plugin-AssetPack.new 
(New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "perl-Mojolicious-Plugin-AssetPack"

Sat May 27 13:19:08 2017 rev:32 rq:498321 version:1.44

Changes:
--------
--- 
/work/SRC/openSUSE:Factory/perl-Mojolicious-Plugin-AssetPack/perl-Mojolicious-Plugin-AssetPack.changes
      2017-05-24 16:47:19.720229294 +0200
+++ 
/work/SRC/openSUSE:Factory/.perl-Mojolicious-Plugin-AssetPack.new/perl-Mojolicious-Plugin-AssetPack.changes
 2017-05-27 13:19:45.391701726 +0200
@@ -1,0 +2,10 @@
+Thu May 25 08:35:52 UTC 2017 - co...@suse.com
+
+- updated to 1.44
+   see /usr/share/doc/packages/perl-Mojolicious-Plugin-AssetPack/Changes
+
+  1.44 2017-05-21T23:02:46+0200
+   - Improved documentation #125
+     Contributor: William Lindley
+
+-------------------------------------------------------------------

Old:
----
  Mojolicious-Plugin-AssetPack-1.43.tar.gz

New:
----
  Mojolicious-Plugin-AssetPack-1.44.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ perl-Mojolicious-Plugin-AssetPack.spec ++++++
--- /var/tmp/diff_new_pack.tL8iPP/_old  2017-05-27 13:19:46.215585251 +0200
+++ /var/tmp/diff_new_pack.tL8iPP/_new  2017-05-27 13:19:46.219584685 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           perl-Mojolicious-Plugin-AssetPack
-Version:        1.43
+Version:        1.44
 Release:        0
 %define cpan_name Mojolicious-Plugin-AssetPack
 Summary:        Compress and convert css, less, sass, javascript and 
coffeescript files
@@ -49,7 +49,9 @@
 while developing, but a minified version in production. This assetpack
 plugin will handle all of that automatically for you.
 
-The actual processing is delegated to "pipe objects". Please see
+Your application creates and refers to an asset by its topic (virtual asset
+name). The process of building actual assets from their components is
+delegated to "pipe objects". Please see
 Mojolicious::Plugin::AssetPack::Guides::Tutorial/Pipes for a complete list.
 
 %prep

++++++ Mojolicious-Plugin-AssetPack-1.43.tar.gz -> 
Mojolicious-Plugin-AssetPack-1.44.tar.gz ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/Mojolicious-Plugin-AssetPack-1.43/Changes 
new/Mojolicious-Plugin-AssetPack-1.44/Changes
--- old/Mojolicious-Plugin-AssetPack-1.43/Changes       2017-05-12 
14:38:02.000000000 +0200
+++ new/Mojolicious-Plugin-AssetPack-1.44/Changes       2017-05-21 
23:02:46.000000000 +0200
@@ -1,5 +1,9 @@
 Revision history for perl distribution Mojolicious-Plugin-AssetPack
 
+1.44 2017-05-21T23:02:46+0200
+ - Improved documentation #125
+   Contributor: William Lindley
+
 1.43 2017-05-12T14:38:02+0200
  - Fix not escaping Vuejs template code
  - Less verbose logging when processing assets
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/Mojolicious-Plugin-AssetPack-1.43/META.json 
new/Mojolicious-Plugin-AssetPack-1.44/META.json
--- old/Mojolicious-Plugin-AssetPack-1.43/META.json     2017-05-12 
14:38:03.000000000 +0200
+++ new/Mojolicious-Plugin-AssetPack-1.44/META.json     2017-05-21 
23:02:47.000000000 +0200
@@ -48,6 +48,6 @@
          "url" : 
"https://github.com/jhthorsen/mojolicious-plugin-assetpack.git";
       }
    },
-   "version" : "1.43",
+   "version" : "1.44",
    "x_serialization_backend" : "JSON::PP version 2.27300_01"
 }
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/Mojolicious-Plugin-AssetPack-1.43/META.yml 
new/Mojolicious-Plugin-AssetPack-1.44/META.yml
--- old/Mojolicious-Plugin-AssetPack-1.43/META.yml      2017-05-12 
14:38:03.000000000 +0200
+++ new/Mojolicious-Plugin-AssetPack-1.44/META.yml      2017-05-21 
23:02:47.000000000 +0200
@@ -25,5 +25,5 @@
   bugtracker: https://github.com/jhthorsen/mojolicious-plugin-assetpack/issues
   homepage: https://github.com/jhthorsen/mojolicious-plugin-assetpack
   repository: https://github.com/jhthorsen/mojolicious-plugin-assetpack.git
-version: '1.43'
+version: '1.44'
 x_serialization_backend: 'CPAN::Meta::YAML version 0.018'
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/Mojolicious-Plugin-AssetPack-1.43/README 
new/Mojolicious-Plugin-AssetPack-1.44/README
--- old/Mojolicious-Plugin-AssetPack-1.43/README        2017-05-12 
14:38:02.000000000 +0200
+++ new/Mojolicious-Plugin-AssetPack-1.44/README        2017-05-21 
23:02:46.000000000 +0200
@@ -3,7 +3,7 @@
     javascript and coffeescript files
 
 VERSION
-    1.43
+    1.44
 
 SYNOPSIS
   Application
@@ -55,8 +55,10 @@
     directly while developing, but a minified version in production. This
     assetpack plugin will handle all of that automatically for you.
 
-    The actual processing is delegated to "pipe objects". Please see "Pipes"
-    in Mojolicious::Plugin::AssetPack::Guides::Tutorial for a complete list.
+    Your application creates and refers to an asset by its topic (virtual
+    asset name). The process of building actual assets from their components
+    is delegated to "pipe objects". Please see "Pipes" in
+    Mojolicious::Plugin::AssetPack::Guides::Tutorial for a complete list.
 
 GUIDES
     * Mojolicious::Plugin::AssetPack::Guides::Tutorial
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/Mojolicious-Plugin-AssetPack-1.43/lib/Mojolicious/Plugin/AssetPack/Guides/Tutorial.pod
 
new/Mojolicious-Plugin-AssetPack-1.44/lib/Mojolicious/Plugin/AssetPack/Guides/Tutorial.pod
--- 
old/Mojolicious-Plugin-AssetPack-1.43/lib/Mojolicious/Plugin/AssetPack/Guides/Tutorial.pod
  2017-04-29 14:22:11.000000000 +0200
+++ 
new/Mojolicious-Plugin-AssetPack-1.44/lib/Mojolicious/Plugin/AssetPack/Guides/Tutorial.pod
  2017-05-21 23:01:47.000000000 +0200
@@ -14,12 +14,12 @@
 
 =head2 Loading the plugin
 
-The plugin need to be installed an loaded before any assets can be defined:
+The plugin needs to be installed an loaded before any assets can be defined:
 
   $app->plugin(AssetPack => \%args);
 
 Details about C<%args> can be found under
-L<Mojolicious::Plugin::AssetPack/register>, but there are one mandatory
+L<Mojolicious::Plugin::AssetPack/register>, but there is one mandatory
 argument worth noting: "pipes". "pipes" need to be a list of all the pipes
 you need to process your assets. Example:
 
@@ -30,7 +30,7 @@
 
 =head2 Optional dependencies
 
-AssetPack only has optional dependencies. The reason for that is that the
+AssetPack has only optional dependencies. The reason for that is that the
 dependencies should only be required while developing, and not for running
 the application. See 
L<https://github.com/jhthorsen/mojolicious-plugin-assetpack/blob/v2/cpanfile>
 for a complete list, but here are the current list:
@@ -126,8 +126,8 @@
 =head3 On disk
 
 AssetPack will look for source files in the "assets" directory, relative to the
-application L<home|Mojo/home>. This directory is not shared on the internet
-like the "public" directory, but the generated assets will still be available
+application L<home|Mojo/home>. Unlike the "public" directory, this directory is
+not shared on the internet, but the generated assets will still be available
 thanks to a custom L<route|Mojolicious::Plugin::AssetPack/route>.
 
 L<Mojolicious::Plugin::AssetPack::Store> is a sub class of
@@ -270,7 +270,7 @@
 
 =head3 Development
 
-The assets will be processed, but not minifed/combined if L<MOJO_MODE> or
+The assets will be processed, but not minified/combined if L<MOJO_MODE> or
 L<Mojolicious/mode> is set to "development". This is to make it easier to
 map JavaScript or CSS bugs to a specific file and line. "development" is
 the default mode while running L<morbo|Mojo::Server::Morbo>:
@@ -286,15 +286,15 @@
 
 Processed assets will be cached to disk when possible. The process step is run
 so if such a processed asset exists, the process step will not be run again.
-This again only require external tools (less, coffee, ...) and modules
-(L<JavaScript::Minifier::XS>, L<CSS::Sass>) to be required while developing,
-but can be skipped when installing an already built application.
+Again, the external tools (less, coffee, ...) and modules
+(L<JavaScript::Minifier::XS>, L<CSS::Sass>) will only be required while
+developing, but can be skipped when installing an already built application.
 
 =head2 Assets without topics
 
 One nifty feature is to use L<Mojolicious::Plugin::AssetPack> for assets which
-does not have any pipe to process them. The reason why this comes in handy is
-to avoid cache issues, since changing the file on disk will generate a new URL.
+do not have any pipe to process them. The reason why this comes in handy is to
+avoid cache issues, since changing the file on disk will generate a new URL.
 
 These assets can also be defined directly in the templates, without having to
 be defined in the application startup process. Examples:
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/Mojolicious-Plugin-AssetPack-1.43/lib/Mojolicious/Plugin/AssetPack.pm 
new/Mojolicious-Plugin-AssetPack-1.44/lib/Mojolicious/Plugin/AssetPack.pm
--- old/Mojolicious-Plugin-AssetPack-1.43/lib/Mojolicious/Plugin/AssetPack.pm   
2017-05-12 14:38:02.000000000 +0200
+++ new/Mojolicious-Plugin-AssetPack-1.44/lib/Mojolicious/Plugin/AssetPack.pm   
2017-05-21 23:02:46.000000000 +0200
@@ -6,7 +6,7 @@
 use Mojolicious::Plugin::AssetPack::Store;
 use Mojolicious::Plugin::AssetPack::Util qw(diag has_ro load_module DEBUG);
 
-our $VERSION = '1.43';
+our $VERSION = '1.44';
 
 my %TAG_TEMPLATE;
 $TAG_TEMPLATE{css} = [qw(link rel stylesheet href)];
@@ -277,7 +277,7 @@
 
 =head1 VERSION
 
-1.43
+1.44
 
 =head1 SYNOPSIS
 
@@ -333,7 +333,9 @@
 while developing, but a minified version in production. This assetpack plugin
 will handle all of that automatically for you.
 
-The actual processing is delegated to "pipe objects". Please see
+Your application creates and refers to an asset by its topic (virtual asset
+name).  The process of building actual assets from their components is
+delegated to "pipe objects". Please see
 L<Mojolicious::Plugin::AssetPack::Guides::Tutorial/Pipes> for a complete list.
 
 =head1 GUIDES


Reply via email to