View Revisions: Issue #4361

Summary 0004361: better directory structure & 'make install' by default (also good for system packages)
Revision 2015-06-14 12:55 by syzop
Additional Information (More or less raw notes..)

We currently have the following:
* unrealircd.conf (user needs to create this)
* example.conf + many translations of this file
* help.conf + many translations of this file
* badwords.*.conf (3 files)
* spamfilter.conf
* dccallow.conf (optional example, normally not included)

I was thinking like:

conf/ - root conf directory
conf/unrealircd.conf - where we expect the unrealircd.conf :)
conf/example/ - for example.*conf
conf/help/ - for help.*conf

so far so good, but how about the rest...

badwords.*.conf is often unchanged, so do we put this in conf/ directory? or in conf/example/ ? (because it still could be customized). Or in conf/badwords/ which may be over-the-top. Similar situation for spamfilter.conf...
Actually, now I think about it: nowadays, when we extract to 3.4-alphaX/ and such, an no longer to the fixed 'Unreal3.2' which we did until a few years ago, you (normally) no longer have that danger of overwriting. So then it's safe to just put things like badwords.*.conf and spamfilter.conf directly in conf/ I think.

Or maybe not conf/ but etc/. I think conf/ is more descriptive though, but etc/ is more standard I guess.
Revision 2015-06-14 12:54 by syzop
Additional Information We currently have the following:
* unrealircd.conf (user needs to create this)
* example.conf + many translations of this file
* help.conf + many translations of this file
* badwords.*.conf (3 files)
* spamfilter.conf
* dccallow.conf (optional example, normally not included)

I was thinking like:

conf/ - root conf directory
conf/unrealircd.conf - where we expect the unrealircd.conf :)
conf/example/ - for example.*conf
conf/help/ - for help.*conf

so far so good, but how about the rest...

badwords.*.conf is often unchanged, so do we put this in conf/ directory? or in conf/example/ ? (because it still could be customized). Or in conf/badwords/ which may be over-the-top. Similar situation for spamfilter.conf...
Actually, now I think about it: nowadays, when we extract to 3.4-alphaX/ and such, an no longer to the fixed 'Unreal3.2' which we did until a few years ago, you (normally) no longer have that danger of overwriting. So then it's safe to just put things like badwords.*.conf and spamfilter.conf directly in conf/ I think.

Or maybe not conf/ but etc/. I think conf/ is more descriptive though, but etc/ is more standard I guess.
Revision 2015-06-14 12:50 by syzop
Additional Information