Re: [RFR] templates://typo3-dummy/{typo3-dummy.templates}
Christian PERRIER wrote:
> Your review should be sent as an answer to this mail.
>
> (indeed, there have been very few changes)
Well, the template did get mentioned on this list earlier this
month, so presumably all the obvious problems got hammered out at
that stage. I'm glad to get a shot at the package description,
though.
> Rationale:
[...]
> This has been changed and newer versions place two new symlinks into
> /etc/apache2/sites-available/. To prevent failures due to
> overlapping configuration directives you should remove the
> symlink typo3-dummy.conf from /etc/apache2/conf.d/ and merge its
> - contents into one of the new .conf files.
> + content into one of the new .conf files.
> s/contents/content
No, undo that. I don't know why "content" is both a "mass" noun and
a countable plural with essentially the same meaning, but
idiomatically here the plural's more normal.
> Depends: exim4 | mail-transport-agent, dbconfig-common, debconf, graphicsmagick, lsb-base (>= 3.0-6), php5, php5-cli, php5-gd, php5-mysql, php5-xcache, typo3-src-4.3, ${misc:Depends}
> Recommends: catdoc, ghostscript, memcached, php5-curl, php5-memcache, ppthtml, typo3-database, unrtf, xlhtml, xpdf-utils
> -Description: TYPO3 - the enterprise level open source WebCMS (Site structure)
> - TYPO3 is a free Open Source content management system for enterprise purposes
> +Description: web content management system
>
> There are other CMS in Debian, so it's definitely not "the"
> CMS. Repeating the software name in the description is useless. And,
> finally, "enterprise level" are buzzwords...:-)
I'd be inclined to keep one use of "enterprise" just to show it's
focussed on businesses, but it certainly doesn't need to be in the
synopsis.
> I guess that "site structure" is here to mean what's explained in the
> last paragraph of the long description, but it is IMHO pointless in
> the synopsis.
In fact putting that together with the slightly odd packagename
makes it sound as if this is a "typo3-common". Leaving it out
implies this is the one to get if you just want to set up a TYPO3
installation, which I gather is how it works.
> + TYPO3 is a content management system for enterprise purposes
> on the web and in intranets. It offers full flexibility and extendability while
> featuring an accomplished set of ready-made interfaces, functions and modules.
This is still a bit clunky (the "accomplished set" feels
half-translated); instead of "offering" lots of abstract nouns it
would be simpler to use adjectives.
TYPO3 is an enterprise-level content management system for use on the web
and in intranets. It is flexible, extensible, and well supplied with
ready-made interfaces, functions, and modules.
> The most important key features of TYPO3 are:
This makes me wonder whether there's such a thing as an unimportant
key feature.
Its key features are:
> + * simple creation of multi-language websites with fallback to a default
> + language;
> + * handling of multi-domain websites within a single page tree;
> + * multi-user backend editing with complete GUI customisation using an
> + advanced ACL system;
Does this mean that the GUI customisation takes place using an
advanced ACL system? I doubt that, so say
* multi-user backend editing via a completely customisable GUI using an
advanced ACL system;
> + * integrated workflow management system based on an multi-step architecture
* an integrated workflow management system based on a multi-tier architecture
(Programs are multi-step, hierarchies are multi-tier)
[...]
> .
> This package provides the basic directory structure to start a new and clean
> website based on TYPO3. This includes a default configuration and some scripts
> to register the site in Apache.
"New and clean" again feels like some sort of idiom translation
failure; maybe "fresh"?
> .
> This package is intended for single vhost installations. TYPO3 can be
> + configured to work with several vhosts and a single src-dir but such
> + setup has to be done manually after installation.
A second paragraph starting with "this package". Would it make
sense to merge them?
This package provides the basic directory structure to start a fresh
website based on TYPO3. It includes scripts to register the site in
Apache, with a default configuration intended for single vhost
installations. TYPO3 can also be configured to work with several vhosts
and a single src-dir, but such setups require some manual configuration.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--- typo3-dummy-4.3.0.pristine/debian/typo3-dummy.templates 2010-05-05 15:56:26.000000000 +0100
+++ typo3-dummy-4.3.0/debian/typo3-dummy.templates 2010-06-02 18:21:48.000000000 +0100
@@ -18,14 +18,15 @@
Type: boolean
_Description: Should apache2 be restarted after installation?
The typo3-dummy package has included the TYPO3 configuration into
- the apache2 configuration and activated the rewrite module. To make
- these changes take effect apache2 must be reloaded.
+ the apache2 configuration and activated the rewrite module. In order
+ for these changes to take effect, apache2 must be reloaded.
Template: typo3-dummy/old_symlink
Type: note
_Description: Old symlink in /etc/apache2/conf.d/
Older versions (before 4.3.0-3) of typo3-dummy installed the apache2
configuration symlink as /etc/apache2/conf.d/typo3-dummy.conf.
+ .
This has been changed and newer versions place two new symlinks into
/etc/apache2/sites-available/. To prevent failures due to
overlapping configuration directives you should remove the
--- typo3-dummy-4.3.0.pristine/debian/control 2010-05-04 22:38:20.000000000 +0100
+++ typo3-dummy-4.3.0/debian/control 2010-06-02 18:27:52.000000000 +0100
@@ -10,28 +10,25 @@
Architecture: all
Depends: exim4 | mail-transport-agent, dbconfig-common, debconf, graphicsmagick, lsb-base (>= 3.0-6), php5, php5-cli, php5-gd, php5-mysql, php5-xcache, typo3-src-4.3, ${misc:Depends}
Recommends: catdoc, ghostscript, memcached, php5-curl, php5-memcache, ppthtml, typo3-database, unrtf, xlhtml, xpdf-utils
-Description: TYPO3 - the enterprise level open source WebCMS (Site structure)
- TYPO3 is a free Open Source content management system for enterprise purposes
- on the web and in intranets. It offers full flexibility and extendability while
- featuring an accomplished set of ready-made interfaces, functions and modules.
+Description: web content management system
+ TYPO3 is an enterprise-level content management system for use on the web
+ and in intranets. It is flexible, extensible, and well supplied with
+ ready-made interfaces, functions, and modules.
.
- The most important key features of TYPO3 are:
- * Simple creation of multi language websites with fallback to a default
- language
- * Handling of multi domain websites within a single page tree
- * Multi user backend editing with complete GUI customisation using an
- advanced ACL system
- * An integrated workflow management system based on an multi step architecture
- with editor and supervisor privileges
- * Unlimited redefinition of the rendering process using the build-in
- TypoScript configuration interface or the plugin API
- * Thousands of plugins are available in the online TYPO3 extension repository
+ Its key features are:
+ * simple creation of multi-language websites with fallback to a default
+ language;
+ * handling of multi-domain websites within a single page tree;
+ * multi-user backend editing via a completely customisable GUI using an
+ advanced ACL system;
+ * an integrated workflow management system based on a multi-tier
+ architecture with editor and supervisor privileges;
+ * unlimited redefinition of the rendering process using the built-in
+ TypoScript configuration interface or the plugin API;
+ * thousands of plugins available in the online TYPO3 extension repository.
.
- This package provides the basic directory structure to start a new and clean
- website based on TYPO3. This includes a default configuration and some scripts
- to register the site in Apache.
- .
- NOTE: This package is intended for single vhost installations. TYPO3 can be
- configured to work with several vhosts and a single src-dir but this package
- can not handle this for you!
-
+ This package provides the basic directory structure to start a fresh
+ website based on TYPO3. It includes scripts to register the site in
+ Apache, with a default configuration intended for single vhost
+ installations. TYPO3 can also be configured to work with several vhosts
+ and a single src-dir, but such setups require some manual configuration.
Source: typo3-dummy
Section: web
Priority: optional
Maintainer: Christian Welzel <gawain@camlann.de>
Homepage: http://www.typo3.com
Build-Depends: debhelper (>= 6.0.7), po-debconf
Standards-Version: 3.8.4
Package: typo3-dummy
Architecture: all
Depends: exim4 | mail-transport-agent, dbconfig-common, debconf, graphicsmagick, lsb-base (>= 3.0-6), php5, php5-cli, php5-gd, php5-mysql, php5-xcache, typo3-src-4.3, ${misc:Depends}
Recommends: catdoc, ghostscript, memcached, php5-curl, php5-memcache, ppthtml, typo3-database, unrtf, xlhtml, xpdf-utils
Description: web content management system
TYPO3 is an enterprise-level content management system for use on the web
and in intranets. It is flexible, extensible, and well supplied with
ready-made interfaces, functions, and modules.
.
Its key features are:
* simple creation of multi-language websites with fallback to a default
language;
* handling of multi-domain websites within a single page tree;
* multi-user backend editing via a completely customisable GUI using an
advanced ACL system;
* an integrated workflow management system based on a multi-tier
architecture with editor and supervisor privileges;
* unlimited redefinition of the rendering process using the built-in
TypoScript configuration interface or the plugin API;
* thousands of plugins available in the online TYPO3 extension repository.
.
This package provides the basic directory structure to start a fresh
website based on TYPO3. It includes scripts to register the site in
Apache, with a default configuration intended for single vhost
installations. TYPO3 can also be configured to work with several vhosts
and a single src-dir, but such setups require some manual configuration.
Template: typo3-dummy/apache_mode
Type: select
__Choices: vhost, directory, none
Default: directory
_Description: Apache integration mode:
Please choose the method that should be used for integrating the
TYPO3 installation with the apache2 web server.
.
vhost: generates shorter URLs with TYPO3 as part of the domain
name, such as http://typo3.example.com/;
directory: fits TYPO3 within the existing site, making it available
at an address like http://www.example.com/cms/;
none: does not configure TYPO3 automatically. The server will
need manual configuration. Choose this option if you are
using a web server other than apache2.
Template: typo3-dummy/apache_restart
Type: boolean
_Description: Should apache2 be restarted after installation?
The typo3-dummy package has included the TYPO3 configuration into
the apache2 configuration and activated the rewrite module. In order
for these changes to take effect, apache2 must be reloaded.
Template: typo3-dummy/old_symlink
Type: note
_Description: Old symlink in /etc/apache2/conf.d/
Older versions (before 4.3.0-3) of typo3-dummy installed the apache2
configuration symlink as /etc/apache2/conf.d/typo3-dummy.conf.
.
This has been changed and newer versions place two new symlinks into
/etc/apache2/sites-available/. To prevent failures due to
overlapping configuration directives you should remove the
symlink typo3-dummy.conf from /etc/apache2/conf.d/ and merge its
contents into one of the new .conf files.
Reply to: