Package: ruby-actionpack-page-caching Severity: wishlist Tags: patch Dear Maintainer,
the long description of this package starts with Static page caching for Action Pack (removed from core in Rails 4.0). which is a duplicate of the short description. I suggest you remove that line and also the trailing white space from some lines and the white space at the beginning of the line "This is the fastest way" which has a special meaning when rendering the description, eg. see https://packages.debian.org/en/sid/ruby-actionpack-page-caching The attached patch remove the duplicated sentence and reflows the rest of the description removing the superfluous spaces. thanks, Daniele
--- debian/control.orig 2015-03-27 12:14:33.000000000 +0100 +++ debian/control 2015-04-03 12:13:19.995589001 +0200 @@ -18,13 +18,12 @@ Breaks: ruby-actionpack-2.3 Replaces: ruby-actionpack-2.3 Description: static page caching for Action Pack (removed from core in Rails 4.0) - Static page caching for Action Pack (removed from core in Rails 4.0). Page - caching is an approach to caching where the entire action output of is stored - as a HTML file that the web server can serve without going through Action Pack. - This is the fastest way to cache your content as opposed to going dynamically - through the process of generating the content. Unfortunately, this incredible - speed-up is only available to stateless pages where all visitors are treated - the same. Content management systems -- including weblogs and wikis -- have - many pages that are a great fit for this approach, but account-based systems - where people log in and manipulate their own data are often less likely + Page caching is an approach to caching where the entire action output of is + stored as a HTML file that the web server can serve without going through + Action Pack. This is the fastest way to cache your content as opposed to going + dynamically through the process of generating the content. Unfortunately, this + incredible speed-up is only available to stateless pages where all visitors are + treated the same. Content management systems -- including weblogs and wikis -- + have many pages that are a great fit for this approach, but account-based + systems where people log in and manipulate their own data are often less likely candidates.
_______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
