On Thu, Aug 12, 2010 at 10:45:38AM -0700, Russ Allbery wrote: > Good point. Here's updated proposed wording. > diff --git a/perl-policy.sgml b/perl-policy.sgml > index 3b76b94..03e5dfb 100644 > --- a/perl-policy.sgml > +++ b/perl-policy.sgml > @@ -128,17 +128,27 @@ > <sect id="paths"> > <heading>Module Path</heading> > <p> > - Perl searches three different locations for modules, referred > - to in this document as <var>core</var> in which modules > - distributed with Perl are installed, <var>vendor</var> for > - packaged modules and <var>site</var> for modules installed by > - the local administrator. > + Perl searches four different locations for modules, referred to > + in this document as <var>etc</var> for system configuration > + modules, <var>core</var> in which modules distributed with Perl > + are installed, <var>vendor</var> for packaged modules, > + and <var>site</var> for modules installed by the local > + administrator. > </p> > <p> > The module search path (<tt>@INC</tt>) in the Debian packages > has been ordered to include these locations in the following > order: > <taglist> > + <tag><var>etc</var></tag> > + <item> > + <p> > + Configuration modules (see <ref id="config_modules">). > + <example> > +/etc/perl > + </example> > + </p> > + </item> > <tag><var>site</var> (current)</tag> > <item> > <p> > @@ -393,6 +403,17 @@ $(MAKE) install DESTDIR=$(CURDIR)/debian/<tmp> > </p> > </sect1> > </sect> > + > + <sect id="config_modules"> > + <heading>Configuration Modules</heading> > + <p> > + Some Perl packages load system-wide configuration from a > + dedicated Perl module whose purpose is solely to contain > + configuration settings. The module often contains only variable > + settings. Such modules should be treated as configuration files > + and installed under <file>/etc/perl</file>. > + </p> > + </sect> > </chapt> > > <chapt id="programs"> Seconded. -- Niko Tyni ntyni@debian.org
Attachment:
signature.asc
Description: Digital signature