keeping include: from overriding directives in the config

Hello list :)

Say I have a config file that I want a user to be able to specify some 
options but not others.

What I was thinking was in the main config file (which the user can read 
but not write) I'd specify the options that I don't want them to be able 
to change and use include: to let them specify any other options in a 
file they can write to.

My question is:

Would it be better to put the include before or after the other directives?

Say they specify "whatever:" in their file but I don't want to allow 
them to change or specify "whatever:"

# if htdig uses the first instance of it then I need to specify it first:

  whatever: they shouldn't be able to change this
  include: their/file

or

# if htdig uses the last instance of it then I need to specify it last 
to override anything they put in:

  include: their/file
  whatever: they shouldn't be able to change this

So which way should I do it to acheive that (IE preventing the include: 
from overriding certain options) and is that even possible?


Danke :)


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
ht://Dig general mailing list: <[email protected]>
ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-general