ship a good ircd.conf by default on install about charybdis

[Heartmender]

Would it be sufficient to add a note for the correct use/placement of example.conf in its header?

[anarcat]

No - the idea here is for the make install target to yield working install.

[sariyamelody]

Personally, I think having a working example configuration upon building is a Bad Thing^tm. Configuration and customization is absolutely crucial for a proper IRC network, and this should be made clear - and it is, in the current configuration. Looking at solutions, I would recommend what Heartmender suggested, notes about the correct placement in the header of example.conf.

Additionally, from quick testing of my own (see below), it appears that attempting to start Charybdis without a configuration file in place does not show any kind of error, it simply stops. Someone please correct me if this is wrong. If this is the current behaviour, however, I would recommend adding a notification to create an ircd.conf if one is not found when running the ircd binary.

[VPS] rylai@crestfall:~/ircd/bin $ ./ircd
  notice: starting charybdis-3.5.0-dev ...
  notice: libratbox version: 20081213_1-26296 - Using SSL: OpenSSL 1.0.1e 11 Feb 2013 compiled: 0x1000105f, library 0x1000105f
[VPS] rylai@crestfall:~/ircd/bin $

[anarcat]

This assumes that people will install charybdis to build a fully-fledged network, whereas it can also be useful to install charybdis to (say) develop IRC bots locally, and the example config is well adapted to that (or should be).

[Heartmender]

quora@fluttershy:~/Prefixes/Chary/bin$ ./ircd
  notice: starting charybdis-3.5.0-dev ...
  notice: libratbox version: 20081213_1-26296 - Using SSL: OpenSSL 1.0.1c 10 May 2012 compiled: 0x1000103f, library 0x1000103f
  notice: FATAL: No config file found at /home/quora/Prefixes/Chary/etc/ircd.conf, exiting

How would this be in addition to renaming example.conf to ircd.conf.example in the same style as Atheme's atheme.conf.example? I feel that a patch like this is best suited for packaging in places like Debian's repositories, and not in the upstream source tree.

[sariyamelody]

@anarcat
That is a possible situation, yes. I still don't think that is reasoning enough for a working ircd.conf out of the box. I could see a barebones.conf example file potentially being included for purposes like that, I guess.

@Heartmender
I do believe that this would be a good idea.

[Heartmender]

Please see adef4da and e3b534d. I am considering this closed as a patch to further rename these files can be introduced to Debian locally.

[anarcat]

I already did, in fact, include that patch in the Debian package. The patch is really silly and unreadable as it removes one file and creates the other, yet there's no change.

I wanted to avoid this confusing and useless change with upstream, but it seems I failed. :)

But since the patch was refused, I will simply drop it on our side and rename the file during the build process instead.