[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

for human consumption (Was: Re: [RFR] templates://nis/{templates})



> Your review should be sent as an answer to this mail.

The revised template looks good; in the control file:

>  Conflicts: netstd (<=1.26)

Drop this; even my Rex CD has netstd 2.07-1!

> +Description: clients and daemons for Network Information Services (NIS)
> 
> Drop leading capital per DevRef recommendations.
> 
> Drop "the": there is not only one "Network Information Services"

As a matter of fact all the other sources I can find say that NIS
stands for "(the) Network Information Service" (singular).  And do
we need a "(NIS)" at the end when the packagename is "nis"?

   Description: clients and daemons for the Network Information Service
 
> + This package allows using NIS services from a NIS server or
> + to set up a NIS server. NIS is mostly used to let several machines
> + in a network share the same account information, such as the password file.
>   NIS was formerly called Yellow Pages (YP).
> 
> Drop "you" and jump into my usual "allows to" nightmare..:-)

Yes, you've got a problem with the second half of that sentence:
it's "This package allows [...] to set up a NIS server", and that's
the objectless construction that isn't allowed.  Besides, there's no
"allowing" involved - "using NIS services from a NIS server" (via
nsswitch) does not require this package.

"Formerly" to me tends to imply that the name change (to the extent
that it happened) was moderately recent.  But it was almost twenty
years ago, so "originally" seems more appropriate.

The whole thing's a bit awkward and repetitive, too - even worse if
you mentally expand "NIS services" to "Network Information Service
services".  The best I can come up with is:

    This package provides tools for setting up and maintaining a NIS domain.
    NIS, originally known as Yellow Pages (YP), is mostly used to let
    several machines in a network share the same account information, such
    as the password file.
-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package
--- ../nis-3.17.pristine/debian/templates	2009-05-08 12:11:14.000000000 +0100
+++ debian/templates	2009-05-12 09:21:43.000000000 +0100
@@ -1,8 +1,10 @@
 Template: nis/domain
 Type: string
-_Default: 
-_Description: NIS domain
- You now need to choose a NIS domainname for your system. If you want this
- machine to just be a client, enter the NIS domainname of your network.
- Otherwise choose an appropriate NIS domainname.
-
+_Description: NIS domain:
+ Please choose the NIS domain name for this system. If you want this
+ machine to just be a client, you should enter the name of the
+ existing NIS domain.
+ .
+ Alternatively, if this machine is planned to be a NIS server, you can
+ either enter a new NIS domain name (which will create that domain) or
+ the name of an existing NIS domain.
--- ../nis-3.17.pristine/debian/control	2009-05-08 12:11:14.000000000 +0100
+++ debian/control	2009-05-12 10:10:57.000000000 +0100
@@ -11,9 +11,8 @@
 Architecture: any
 Pre-Depends: debconf (>= 0.5.00) | debconf-2.0
 Depends: ${shlibs:Depends}, netbase, make, portmap, lsb-base (>= 3.0-6)
-Conflicts: netstd (<=1.26)
-Description: Clients and daemons for the Network Information Services (NIS)
- The nis package allows you to use the NIS services from a NIS server or
- to set up your own NIS server. NIS is mostly used to let several machines
- in a network share the same account information (eg the password file).
- NIS was formerly called Yellow Pages (YP).
+Description: clients and daemons for the Network Information Service
+ This package provides tools for setting up and maintaining a NIS domain.
+ NIS, originally known as Yellow Pages (YP), is mostly used to let
+ several machines in a network share the same account information, such
+ as the password file.
Template: nis/domain
Type: string
_Description: NIS domain:
 Please choose the NIS domain name for this system. If you want this
 machine to just be a client, you should enter the name of the
 existing NIS domain.
 .
 Alternatively, if this machine is planned to be a NIS server, you can
 either enter a new NIS domain name (which will create that domain) or
 the name of an existing NIS domain.
Source: nis
Section: net
Priority: extra
Maintainer: Mark Brown <broonie@debian.org>
Uploaders: Miquel van Smoorenburg <miquels@cistron.nl>
Standards-Version: 3.8.1
Build-Depends: libgdbm-dev, gcc (>= 2.95), gettext, po-debconf, libslp-dev, libdbus-glib-1-dev, network-manager-dev, file
Vcs-Bzr: http://bzr.debian.org/bzr/pkg-nis/nis/debian/

Package: nis
Architecture: any
Pre-Depends: debconf (>= 0.5.00) | debconf-2.0
Depends: ${shlibs:Depends}, netbase, make, portmap, lsb-base (>= 3.0-6)
Description: clients and daemons for the Network Information Service
 This package provides tools for setting up and maintaining a NIS domain.
 NIS, originally known as Yellow Pages (YP), is mostly used to let
 several machines in a network share the same account information, such
 as the password file.

Reply to: