innfeed.conf vs incoming.conf

["Miquel van Smoorenburg"]

In article <cgl8sf$9h0$1 at gatekeeper.tmr.com>,
Bill Davidsen  <davidsen at tmr.com> wrote:
>Miquel van Smoorenburg wrote:
>
>> I understand that in inn 2.5 or 2.6 the newsfeeds, incoming.conf and
>> innfeed.conf files are going to be merged ... FINALLY :)
>
>Let's hope not! Each of these files controls a single characteristic of 
>the system and is not related to the others in a deterministic fashion. 
>That is, changes in incoming.conf don't cause or require changes in 
>newsfeeds or innfeed.conf, changes in newsfeeds don't require changes in 
>incoming.conf and may or may not cause changes in innfeed.conf, etc.
>
>While it does make for more files to edit, each has a single purpose, 
>and is therefore much easier to understand (ie. explain to newbies). 

Really. My experience has been the exact opposite. Also, it's
really hard to keep the 3 files in sync.

If the syntax was unified, you could easily choose to keep
innfeed.conf/incoming.conf/newsfeeds in 3 different files,
_or_ tell the system to use the same file for them. For example
innfeed would simply ignore the incoming.conf/newsfeeds parts.

>Having all the functions in a single file would make that file far more 
>complex, and subject to small errors having large effect.

Again, right now my experience is the exact opposite.

>Now if someone would totally rethink readers.conf and make that usable 
>without a manpage or daily use, that would be most nice.

Now that I agree with.

Mike.
-- 
"In times of universal deceit, telling the truth becomes
 a revolutionary act." -- George Orwell.

-- 
The From: and Reply-To: addresses are internal news2mail gateway addresses.
Reply to the list or to "Miquel van Smoorenburg" <miquels at cistron.nl>