Re: [ngIRCd-ML] Make all channels permanent, by default?

2018-03-25 Thread Alexander Barton
Hi Duncan, Am 20.03.2018 um 07:40 schrieb Duncan Bayne : Alexander Barton writes: There is a quite simple test suite that checks basic functionality: you can run it using "make check". It requires expect(1) and telnet(1) to be available. Great, thanks :) Do you see my change (configurable

Re: [ngIRCd-ML] Make all channels permanent, by default?

2018-03-19 Thread Duncan Bayne
Alexander Barton writes: > There is a quite simple test suite that checks basic functionality: you > can run it using "make check". It requires expect(1) and telnet(1) to be > available. Great, thanks :) Do you see my change (configurable permanent channels by default) being something tested at

Re: [ngIRCd-ML] Make all channels permanent, by default?

2018-03-19 Thread Alexander Barton
Am 17.03.2018 um 23:51 schrieb Duncan Bayne : Alexander Barton writes: GitHub ("pull request") ist the best, but plain patches work as well. Right, I've forked it and will raise a PR as soon as three children, a surprise house-guest, and a full-time job allow :) One final question: is there

Re: [ngIRCd-ML] Make all channels permanent, by default?

2018-03-18 Thread Duncan Bayne
Götz Hoffart writes: >> If there isn't, would you like me to contribute one? > > contrib/platformtest.sh could help? That's the sort of thing; I was imagining perhaps an extension to that that would spin up ngIRCd with known configurations (i.e. with, and without, my new setting) and test that t

Re: [ngIRCd-ML] Make all channels permanent, by default?

2018-03-17 Thread Götz Hoffart
Am 17.03.2018 um 23:51 schrieb Duncan Bayne : > One final question: is there a test suite of some sort? I was planning > to spin up an instance and test it with a client, manually, but figure > some sort of test harness to do that automagically would be nice. > > If there isn't, would you like m

Re: [ngIRCd-ML] Make all channels permanent, by default?

2018-03-17 Thread Duncan Bayne
Alexander Barton writes: > GitHub ("pull request") ist the best, but plain patches work as well. Right, I've forked it and will raise a PR as soon as three children, a surprise house-guest, and a full-time job allow :) One final question: is there a test suite of some sort? I was planning to s

Re: [ngIRCd-ML] Make all channels permanent, by default?

2018-03-16 Thread Alexander Barton
Am 16.03.2018 um 07:20 schrieb Duncan Bayne : Alexander Barton writes: Would you be interested in a pull request / patch to make that behaviour configurable, or is that sufficiently niche that I should just run my own fork? If you’d be willing to share your code/patch, that would be great!

Re: [ngIRCd-ML] Make all channels permanent, by default?

2018-03-15 Thread Duncan Bayne
Alexander Barton writes: >> Would you be interested in a pull request / patch to make that >> behaviour configurable, or is that sufficiently niche that I should >> just run my own fork? > > If you’d be willing to share your code/patch, that would be great! > > And if it isn’t to special and has

Re: [ngIRCd-ML] Make all channels permanent, by default?

2018-03-15 Thread Alexander Barton
Hi Duncan! Am 14.03.2018 um 07:30 schrieb Duncan Bayne : > Alexander Barton writes: > >> Canels are only "persistent" (exist even when no users are joined to >> them) when they are +P, and this mode can only be set >> >> - in the configuration file(s) or >> - by IRC operators during runtime. >>

Re: [ngIRCd-ML] Make all channels permanent, by default?

2018-03-13 Thread Duncan Bayne
Alexander Barton writes: > Canels are only "persistent" (exist even when no users are joined to > them) when they are +P, and this mode can only be set > > - in the configuration file(s) or > - by IRC operators during runtime. > > If set during runtime, this information isn't saved and therefor

Re: [ngIRCd-ML] Make all channels permanent, by default?

2018-03-11 Thread Alexander Barton
Hi Duncan! Am 27.02.2018 um 07:27 schrieb Duncan Bayne : I'm trying to use ngircd in such a manner that all channels are: (a) persisted by default, even if created by non-privileged users, and (b) persisted between restarts of the daemon From reading the docs I gather (b) 'just happens' with