procmail
[Top] [All Lists]

Re: INCLUDERC's vs Monolithic .procmailrc's

2000-09-26 16:03:54
So David, if I understand what you're saying, it's a user 
preference thing unless there was truly *massive* load on the server?
Your point about the user thinking of a set of recipes as a 
separate module was what induced me to try the INCLUDERC direcive 
initially, [although I doubt if I'll ever graduate to recursive code :-)]

Sean's point about "simple to manage" was also what steered me in 
that direction too (or was that laziness perchance?)

Frankly I was awed by Jari's procmailrc, but what a size!! Even as 
meticulously commented and sectioned as it is (thanks Jari!!!), 
it' still somewhat of a labor to wade through it to the sections 
that require constant modification.

Anyway, thanks for the guidance, Sean you also.
-Colin
--
Colin J. Raven
HDS Lab, Inc.
Harrison, NY

-----Original Message-----
From: procmail-admin(_at_)Lists(_dot_)RWTH-Aachen(_dot_)DE
[mailto:procmail-admin(_at_)Lists(_dot_)RWTH-Aachen(_dot_)DE]On Behalf Of 
David W. Tamkin
Sent: Tuesday, September 26, 2000 10:54 AM
To: Procmail Mailing List
Subject: Re: INCLUDERC's vs Monolithic .procmailrc's

Colin asked,

| Can anyone comment on the reasons one should/should not use a single
| "monolithic" .procmailrc as opposed to one .procmailrc *plus* several
| "INCLUDERC" files?

Sometimes a single INCLUDERC needs to be called from several different
places, and it's easier to have one copy in a separate file (and that
way improvements to it are of benefit everywhere it's used) instead of
repetitions of it everywhere in a monolithic .procmailrc.

Sometimes the user thinks of a set of recipes as a separate 
module and it's
easier for him/her to follow the main .procmailrc when (s)he edits it if 
the separate module is out of the way in a separate file.

In a few situations, one needs recursive code; an INCLUDERC is 
the only way
to pull that off.

And in many cases, it's just the user's preference one way or the 
other.  I'd
have to guess that using an INCLUDERC is slightly more load 
(keeping another
file descriptor open, bookmarking the position in two rcfiles at 
once), but
the purpose of computers is to use CPU cycles instead of brain cycles and
free up brain cycles for other things, so if it makes it easier on 
the human, it's worth it.


_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

<Prev in Thread] Current Thread [Next in Thread>