Re: [RFR] templates://zephyr/{zephyr-clients.templates,zephyr-server.templates }
Christian Perrier wrote:
> Your review should be sent as an answer to this mail.
I'm afflicted by power outages, so I'll be a bit slower than usual.
> Template: zephyr-clients/servers
(And likewise in zephyr-server/servers)
> + Please specify the space-separated list of full names for the Zephyr servers.
Selecting them by name or naming them? Assuming the former, say:
Please specify the full names of the Zephyr servers, as a space-separated
list.
> + The list configured on clients can be only a subset of the list configured
> + on servers.
"Can be only" naturally gets interpreted as "cannot be more than"
(as in "there can be only one"). Just drop the "only".
> + This can be left empty if Hesiod is used to advertize Zephyr servers.
Localization gotcha: it's -ise, even in en_US:
"http://m-w.com/cgi-bin/dictionary?va=advertise";
> -Description: The original "Instant Message" system libraries without Kerberos
> - This is the Project Athena Zephyr notification system 2000/04/21 snapshot.
> +Description: Project Athena's instant messaging service - non-Kerberos libraries
>
> Use the "generic - specific" style for the synopsis.
The short descriptions get a bit long with this "instant messaging",
though. And later synopses have "with/without Kerberos support";
I'm standardising them to "foo with Kerberos" but "non-Kerberos foo"
just to save characters.
Description: Project Athena's notification system - non-Kerberos libraries
This is a snapshot of Zephyr, derived from the original Project Athena
'Instant Message' system.
Or given that it's such an old "snapshot" maybe you're right and
users don't need to be told. In which case, merge it into the next
bit:
Description: Project Athena's notification system - non-Kerberos libraries
Zephyr is derived from the original Project Athena 'Instant
Message' system and allows users to send messages...
> Package: zephyr-clients
[...]
> + This package provides client programs for the messaging service. They
> + require a Zephyr server for being fully operationnal.
It's only slightly wrong, but I'm not seeing a simple fix so try:
This package provides client programs for the messaging service. A
Zephyr server is also required.
> Package: zephyr-server
(And zephyr-server-krb)
> + This package provides the server for the messaging service. Only one
> + server is needed for a group of client. The program consumes much memory,
> + especially for very large sites.
> .
> The server maintains a location and subscription database for all the
> receiving clients. All zephyrgrams are sent to the server to be routed
> to the intended recipient.
It seems to me that this is one paragraph:
This package provides the server for the messaging service, which
maintains a location and subscription database for all the receiving
clients. All zephyrgrams are sent to the server to be routed to the
intended recipient. This can be memory-intensive, especially for very
large sites, but only one server is required for a group of clients.
> Package: libzephyr-dev
[...]
> - This package is needed to compile certain other zephyr clients. There are
> - various other clients available, including a totally gratuitous Motif client,
> - a Tcl client, several Emacs clients, and a number of X clients.
[...]
> + This package provides development libraries and files. It is needed
> + to compile alternative Zephyr clients, such as a free (as in free
> + beer) Motif client, a Tcl client, several Emacs clients, and a number
> + of X clients.
>
> Same changes PLUS rewording the last paragraph (the "gratuitous" thing
> doesn't sound well for me...but others might disagree and my proposal
> may be not perfect as well.
I'm afraid in English the meaning of the word "gratuitous" has
shifted from "free/complimentary" to "superfluous/pointless".
But it's slightly slangy, so perhaps it should be dropped.
This package provides development libraries and files, which are
needed to compile alternative Zephyr clients. Available versions
include a (pointless) Motif client, a Tcl client, several Emacs
clients, and a number of X clients.
Or perhaps reorder it to "a Tcl client, several Emacs clients, a
number of X clients, and even a Motif client"? But wait, how are
the Motif and Tcl clients not X clients, anyway?
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--- ../zephyr.old/debian/zephyr-clients.templates 2007-11-07 17:36:12.000000000 +0000
+++ debian/zephyr-clients.templates 2007-11-13 21:09:38.000000000 +0000
@@ -1,10 +1,13 @@
Template: zephyr-clients/servers
Type: string
_Description: Zephyr servers:
- Please type the full names of your zephyr servers, separated by spaces.
- (note that this can be a subset of what you're telling the servers)
- If you are using hesiod to advertise your zephyr servers, leave this
- blank.
+ Please specify the full names of the Zephyr servers, as a space-separated
+ list
+ .
+ The list configured on clients can be a subset of the list configured on
+ servers.
+ .
+ This can be left empty if Hesiod is used to advertise Zephyr servers.
Template: zephyr-clients/read_conf
Type: boolean
--- ../zephyr.old/debian/zephyr-server.templates 2007-11-07 17:36:12.000000000 +0000
+++ debian/zephyr-server.templates 2007-11-13 21:10:10.000000000 +0000
@@ -1,8 +1,11 @@
Template: zephyr-server/servers
Type: string
_Description: Zephyr servers:
- Please type the full names of your zephyr servers, separated by spaces.
- (Note that this can be a superset of that you're telling the clients.)
+ Please specify the full names of the Zephyr servers, as a space-separated
+ list.
+ .
+ The list configured on clients can be a subset of the list configured on
+ servers.
Template: zephyr-server/read_conf
Type: boolean
--- ../zephyr.old/debian/control 2007-11-07 17:36:12.000000000 +0000
+++ debian/control 2007-11-13 21:27:08.000000000 +0000
@@ -11,11 +11,14 @@
Architecture: any
Depends: ${shlibs:Depends}
Conflicts: libzephyr3-krb
-Description: The original "Instant Message" system libraries without Kerberos
- This is the Project Athena Zephyr notification system 2000/04/21 snapshot.
- Zephyr allows users to send messages to other users or to groups of
- users. Users can view incoming Zephyr messages as windowgrams
- (transient X windows) or as text on a terminal.
+Description: Project Athena's notification service - non-Kerberos libraries
+ Zephyr is derived from the original Project Athena 'Instant Message' system
+ and allows users to send messages to other users or to groups of users.
+ Users can view incoming Zephyr messages as windowgrams (transient X
+ windows) or as text on a terminal.
+ .
+ This package provides the libraries without Kerberos support for message
+ authentication.
Package: libzephyr3-krb
Section: libs
@@ -23,75 +26,78 @@
Depends: ${shlibs:Depends}, krb4-config
Conflicts: libzephyr3
Provides: libzephyr3
-Description: The original "Instant Message" system libraries with Kerberos
- This version of the library uses Kerberos for message authentication.
+Description: Project Athena's notification service - libraries with Kerberos
+ Zephyr is derived from the original Project Athena 'Instant Message' system
+ and allows users to send messages to other users or to groups of users.
+ Users can view incoming Zephyr messages as windowgrams (transient X
+ windows) or as text on a terminal.
.
- This is the Project Athena Zephyr notification system 2000/04/21 snapshot.
- Zephyr allows users to send messages to other users or to groups of
- users. Users can view incoming Zephyr messages as windowgrams
- (transient X windows) or as text on a terminal.
+ This package provides libraries that use Kerberos for message
+ authentication.
Package: zephyr-clients
Section: net
Replaces: zephyr-client
Architecture: any
Depends: ${shlibs:Depends}, debianutils (>= 1.6), debconf | debconf-2.0
-Description: The original "Instant Message" system client
- This package only contains the clients; you'll need a server to talk to.
+Description: Project Athena's notification service - client programs
+ Zephyr is derived from the original Project Athena 'Instant Message' system
+ and allows users to send messages to other users or to groups of users.
+ Users can view incoming Zephyr messages as windowgrams (transient X
+ windows) or as text on a terminal.
.
- This is the Project Athena Zephyr notification system 2000/04/21 snapshot.
- Zephyr allows users to send messages to other users or to groups of
- users. Users can view incoming Zephyr messages as windowgrams
- (transient X windows) or as text on a terminal.
+ This package provides client programs for the messaging service. They
+ require a Zephyr server for being fully operationnal.
Package: zephyr-server
Section: net
Architecture: any
Depends: ${shlibs:Depends}, debconf | debconf-2.0
Conflicts: zephyr-server-krb
-Description: The original "Instant Message" system-server without Kerberos
- You probably only need one server for a group of clients.
- This can be a memory-intensive server, especially for very large sites.
- .
- The server maintains a location and subscription database for all the
- receiving clients. All zephyrgrams are sent to the server to be routed
- to the intended recipient.
- .
- This is the Project Athena Zephyr notification system 2000/04/21 snapshot.
- Zephyr allows users to send messages to other users or to groups of
- users. Users can view incoming Zephyr messages as windowgrams
- (transient X windows) or as text on a terminal.
+Description: Project Athena's notification service - non-Kerberos server
+ Zephyr is derived from the original Project Athena 'Instant Message' system
+ and allows users to send messages to other users or to groups of users.
+ Users can view incoming Zephyr messages as windowgrams (transient X
+ windows) or as text on a terminal.
+ .
+ This package provides the server for the messaging service, which
+ maintains a location and subscription database for all the receiving
+ clients. All zephyrgrams are sent to the server to be routed to the
+ intended recipient. This can be memory-intensive, especially for very
+ large sites, but only one server is required for a group of clients.
Package: zephyr-server-krb
Section: net
Architecture: any
Depends: ${shlibs:Depends}, debconf | debconf-2.0, libzephyr3-krb
Conflicts: zephyr-server
-Description: The original "Instant Message" system-server with Kerberos
- You probably only need one server for a group of clients.
- This can be a memory-intensive server, especially for very large sites.
+Description: Project Athena's notification service - server with Kerberos
+ Zephyr is derived from the original Project Athena 'Instant Message' system
+ and allows users to send messages to other users or to groups of users.
+ Users can view incoming Zephyr messages as windowgrams (transient X
+ windows) or as text on a terminal.
+ .
+ This package provides the server for the messaging service. Only one
+ server is needed for a group of client. The program consumes much memory,
+ especially for very large sites.
.
The server maintains a location and subscription database for all the
receiving clients. All zephyrgrams are sent to the server to be routed
to the intended recipient.
.
This version of the server uses Kerberos for message authentication.
- .
- This is the Project Athena Zephyr notification system 2000/04/21 snapshot.
- Zephyr allows users to send messages to other users or to groups of
- users. Users can view incoming Zephyr messages as windowgrams
- (transient X windows) or as text on a terminal.
Package: libzephyr-dev
Section: libdevel
Architecture: any
Depends: libzephyr3 (= ${binary:Version}) | libzephyr3-krb (= ${binary:Version}), libc6-dev
-Description: The original "Instant Message" system development libraries
- This package is needed to compile certain other zephyr clients. There are
- various other clients available, including a totally gratuitous Motif client,
- a Tcl client, several Emacs clients, and a number of X clients.
- .
- This is the Project Athena Zephyr notification system 2000/04/21 snapshot.
- Zephyr allows users to send messages to other users or to groups of
- users. Users can view incoming Zephyr messages as windowgrams
- (transient X windows) or as text on a terminal.
+Description: Project Athena's notification service - development files
+ Zephyr is derived from the original Project Athena 'Instant Message' system
+ and allows users to send messages to other users or to groups of users.
+ Users can view incoming Zephyr messages as windowgrams (transient X
+ windows) or as text on a terminal.
+ .
+ This package provides development libraries and files, which are
+ needed to compile alternative Zephyr clients. Available versions
+ include a (pointless) Motif client, a Tcl client, several Emacs
+ clients, and a number of X clients.
Template: zephyr-clients/servers
Type: string
_Description: Zephyr servers:
Please specify the full names of the Zephyr servers, as a space-separated
list
.
The list configured on clients can be a subset of the list configured on
servers.
.
This can be left empty if Hesiod is used to advertise Zephyr servers.
Template: zephyr-clients/read_conf
Type: boolean
Default: true
Description: for internal use
We want to try and capture user changes when they edit a config file
manually. To do this we look at the file in the config script. However,
in the case of preconfigure, the config script is run twice before the
postinst is run. Thus we may read the wrong value before the edited value
is written out in postinst. If this is false we skip reading config files
until postinst runs.
Template: zephyr-server/servers
Type: string
_Description: Zephyr servers:
Please specify the full names of the Zephyr servers, as a space-separated
list.
.
The list configured on clients can be a subset of the list configured on
servers.
Template: zephyr-server/read_conf
Type: boolean
Default: true
Description: for internal use
We want to try and capture user changes when they edit a config file
manually. To do this we look at the file in the config script. However,
in the case of preconfigure, the config script is run twice before the
postinst is run. Thus we may read the wrong value before the edited value
is written out in postinst. If this is false we skip reading config files
until postinst runs.
Source: zephyr
Section: net
Priority: optional
Maintainer: Karl Ramm <kcr@debian.org>
Uploaders: Karl Ramm <kcr@debian.org>, Sam Hartman <hartmans@debian.org>
Build-Depends: debhelper (>= 4), libares-dev, libkrb5-dev (>= 1.2.2-4), comerr-dev, ss-dev, libreadline5-dev, libx11-dev, libxt-dev, x-dev, libxaw7-dev | libxaw8-dev, libxmu-dev, libncurses5-dev, bison, libhesiod-dev
Standards-Version: 3.7.2.2
Package: libzephyr3
Section: libs
Architecture: any
Depends: ${shlibs:Depends}
Conflicts: libzephyr3-krb
Description: Project Athena's notification service - non-Kerberos libraries
Zephyr is derived from the original Project Athena 'Instant Message' system
and allows users to send messages to other users or to groups of users.
Users can view incoming Zephyr messages as windowgrams (transient X
windows) or as text on a terminal.
.
This package provides the libraries without Kerberos support for message
authentication.
Package: libzephyr3-krb
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, krb4-config
Conflicts: libzephyr3
Provides: libzephyr3
Description: Project Athena's notification service - libraries with Kerberos
Zephyr is derived from the original Project Athena 'Instant Message' system
and allows users to send messages to other users or to groups of users.
Users can view incoming Zephyr messages as windowgrams (transient X
windows) or as text on a terminal.
.
This package provides libraries that use Kerberos for message
authentication.
Package: zephyr-clients
Section: net
Replaces: zephyr-client
Architecture: any
Depends: ${shlibs:Depends}, debianutils (>= 1.6), debconf | debconf-2.0
Description: Project Athena's notification service - client programs
Zephyr is derived from the original Project Athena 'Instant Message' system
and allows users to send messages to other users or to groups of users.
Users can view incoming Zephyr messages as windowgrams (transient X
windows) or as text on a terminal.
.
This package provides client programs for the messaging service. They
require a Zephyr server for being fully operationnal.
Package: zephyr-server
Section: net
Architecture: any
Depends: ${shlibs:Depends}, debconf | debconf-2.0
Conflicts: zephyr-server-krb
Description: Project Athena's notification service - non-Kerberos server
Zephyr is derived from the original Project Athena 'Instant Message' system
and allows users to send messages to other users or to groups of users.
Users can view incoming Zephyr messages as windowgrams (transient X
windows) or as text on a terminal.
.
This package provides the server for the messaging service, which
maintains a location and subscription database for all the receiving
clients. All zephyrgrams are sent to the server to be routed to the
intended recipient. This can be memory-intensive, especially for very
large sites, but only one server is required for a group of clients.
Package: zephyr-server-krb
Section: net
Architecture: any
Depends: ${shlibs:Depends}, debconf | debconf-2.0, libzephyr3-krb
Conflicts: zephyr-server
Description: Project Athena's notification service - server with Kerberos
Zephyr is derived from the original Project Athena 'Instant Message' system
and allows users to send messages to other users or to groups of users.
Users can view incoming Zephyr messages as windowgrams (transient X
windows) or as text on a terminal.
.
This package provides the server for the messaging service. Only one
server is needed for a group of client. The program consumes much memory,
especially for very large sites.
.
The server maintains a location and subscription database for all the
receiving clients. All zephyrgrams are sent to the server to be routed
to the intended recipient.
.
This version of the server uses Kerberos for message authentication.
Package: libzephyr-dev
Section: libdevel
Architecture: any
Depends: libzephyr3 (= ${binary:Version}) | libzephyr3-krb (= ${binary:Version}), libc6-dev
Description: Project Athena's notification service - development files
Zephyr is derived from the original Project Athena 'Instant Message' system
and allows users to send messages to other users or to groups of users.
Users can view incoming Zephyr messages as windowgrams (transient X
windows) or as text on a terminal.
.
This package provides development libraries and files, which are
needed to compile alternative Zephyr clients. Available versions
include a (pointless) Motif client, a Tcl client, several Emacs
clients, and a number of X clients.
Reply to: