[Resolvconf-devel] [LCFC] templates://resolvconf/{templates}

Mon Feb 4 06:45:07 UTC 2008

This is the last call for comments for the review of debconf
templates for resolvconf.

The reviewed templates will be sent on Wednesday, February 06, 2008 to the package
maintainer as a bug report and a mail will be sent to this list with
"[BTS]" as a subject tag.

Please note the following:

1) I finally did "s/nameserver/name server". That may be debatable, so
   please comment

2) I have a doubt for "configurers". ispell complains about it

-- 

-------------- next part --------------
Template: resolvconf/linkify-resolvconf
Type: boolean
Default: true
_Description: Prepare /etc/resolv.conf for dynamic updates?
 The resolvconf package contains the infrastructure required for
 dynamic updating of the resolver configuration file. Part of the
 necessary infrastructure is a symbolic link from /etc/resolv.conf to
 /etc/resolvconf/run/resolv.conf. If you choose this option then this
 link will be created. The existing /etc/resolv.conf file will be
 preserved as /etc/resolvconf/resolv.conf.d/original, and will be
 restored if this package is removed.
 .
 Declining this option will prevent future installations from
 recreating the symbolic link and therefore the resolver configuration
 file will not be dynamically updated. Dynamic updating can then be
 activated following instructions in the README file.
 .
 The presence of resolvconf can affect the behavior of other programs,
 so it should not be left installed if unconfigured.

Template: resolvconf/downup-interfaces
Type: note
_Description: Network interfaces configuration mandatory
 Once resolvconf is installed, interface configurers supply name server
 information to it (which it then makes available to the C library resolver
 and to DNS caches). However, they do this only when they bring up interfaces.
 Therefore for resolvconf's name server information to be up to date after
 initial installation it is necessary to reconfigure interfaces (that is,
 to take them down and then to bring them up again) and to restart
 DNS caches.

Template: resolvconf/link-tail-to-original
Type: boolean
Default: false
_Description: Append original file to dynamic file?
 If the original static resolver configuration file (/etc/resolv.conf)
 contains name server addresses, those addresses should be listed on
 "dns-nameservers" lines in /etc/network/interfaces as described in the
 README file.
 .
 Until /etc/network/interfaces has been edited and the affected
 interfaces brought down and up again, the nameservers addresses will
 not be included in the dynamically generated resolver configuration
 file.
 .
 If you choose this option, a temporary workaround will be put in
 place: a symbolic link will be created (if it does not already exist)
 from /etc/resolvconf/resolv.conf.d/tail to
 /etc/resolvconf/resolv.conf.d/original. This will cause the whole of
 that original resolver configuration file to be appended to the
 dynamically generated file.
 .
 After the required "dns-nameservers" lines have been added to
 /etc/network/interfaces, the /etc/resolvconf/resolv.conf.d/tail link
 should be replaced by one to /dev/null.
-------------- next part --------------
Source: resolvconf
Section: net
Priority: optional
Maintainer: resolvconf maintainers <resolvconf-devel at lists.alioth.debian.org>
Uploaders: Eric Evans <eevans at sym-link.com>, Daniel Kahn Gillmor <dkg at fifthhorseman.net>, Marc Haber <mh+debian-packages at zugschlus.de>, Thomas Hood <jdthood at yahoo.co.uk>, Marco Nenciarini <mnencia at debian.org>
Build-Depends: debhelper (>= 5)
Standards-Version: 3.7.2.1

Package: resolvconf
Architecture: all
Enhances: dhcp3-client (>= 3.0+3.0.1rc11-5), dhcp-client (>= 2.0pl5-18), dhcpcd (>= 1:1.3.22pl4-9), pump (>= 0.8.19), udhcpc (>= 0.9.8cvs20050124-3), ppp (>= 2.4.2), ifupdown (>= 0.6.4-4.7), network-manager, bind9 (>= 1:9.2.3-1), bind (>= 1:8.4.1-2), dnsmasq (>= 2.9-2), pdnsd (>= 1.1.11par-1), totd (>= 1.4-4), libc6, nscd
Depends: coreutils (>= 5.93), lsb-base (>= 3.0-9), ${misc:Depends}
Conflicts: pppconfig (<< 2.3.1), pppoeconf (<< 1.0), xisp, webmin (<< 1.150-2), webmin-wvdial (<< 1.160-3), dhcp3-client (<< 3.0+3.0.1rc11-5), dhcp-client (<< 2.0pl5-18), dhcp-client (= 3.0.1betaRC4-1), dhcpcd (<< 1:1.3.22pl4-7), pump (<< 0.8.15-1), udhcpc (<< 0.9.8cvs20050124-3), pcmcia-cs (<< 3.2.5-1), ifupdown (<< 0.6.4-4.1), divine, laptop-net (<< 2.21-1), whereami (<< 0.3.3), bind9 (<< 1:9.2.1-7), bind (<< 1:8.3.4-1), dnsmasq (<< 1.13-2), pdnsd (<< 1.1.10par-4), totd (<< 1.4-4)
Description: nameservers information handler
 Resolvconf is a framework for keeping track of the system's
 information about currently available nameservers. It sets
 itself up as the intermediary between programs that supply
 nameservers information and programs that use nameservers
 information. Examples of programs that supply nameservers
 information are: ifupdown, DHCP clients, the PPP daemon and
 local nameservers. Examples of programs that use this
 information are: DNS caches, resolver libraries and the
 programs that use them.
 .
 This package may require some manual configuration. Please
 read the README file for detailed instructions.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/resolvconf-devel/attachments/20080204/87c5e832/attachment.pgp 