source@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: cvsweb: delete conf.d madness: it is *always* a terrible idea for *any*
Date: Tue, 26 Nov 2019 06:08:46 -0500 (EST)	[thread overview]
Message-ID: <8d0794efbd9cf031@mandoc.bsd.lv> (raw)

Log Message:
-----------
delete conf.d madness:
it is *always* a terrible idea for *any* program
because it makes the configuration unreadble, wasting sysadmin time

Modified Files:
--------------
    cvsweb:
        cvsweb.conf

Revision Data
-------------
Index: cvsweb.conf
===================================================================
RCS file: /home/cvs/mandoc/cvsweb/cvsweb.conf,v
retrieving revision 4.9
retrieving revision 4.10
diff -Lcvsweb.conf -Lcvsweb.conf -u -p -r4.9 -r4.10
--- cvsweb.conf
+++ cvsweb.conf
@@ -511,23 +511,6 @@ $ENV{CVSREADONLYFS} = 1 unless exists($E
 #
 #$DEBUG = 1;
 
-# Enable this to let CVSweb load extra configuration files from the "conf.d"
-# subdirectory of the directory this file is located in.  This enables site
-# specific configuration without having to modify this "master" configuration
-# file (except for enabling this functionality below :)
-#
-if (0) {
-  my $confdir = catdir(dirname(__FILE__), 'conf.d');
-  if (opendir(CONFD, $confdir)) {
-    my @files = sort(map(catfile($confdir, $_), readdir(CONFD)));
-    close(CONFD);
-    for my $conffile (grep(-f && -r _, @files)) {
-      ($conffile) = ($conffile =~ /(.+\.conf)$/) or next;
-      do "$conffile" or config_error($conffile, $@);
-    }
-  }
-}
-
 1;
 
 # EOF
--
 To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv

                 reply	other threads:[~2019-11-26 11:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8d0794efbd9cf031@mandoc.bsd.lv \
    --to=schwarze@mandoc.bsd.lv \
    --cc=source@mandoc.bsd.lv \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).