Hi,
being the only active maintainer of ejabberd in Debian for almost 2
years, my decision stands: I won't change this back.
If you don't want to divert from upstream, you shouldn't use this
package at all. Although I brought it much closer to upstream, it still
diverts in quite a few ways.
Now,
On Tue, 2015-07-14 at 07:24 +0200, Philipp Huebner wrote:
> No. It's changed already for Jessie which is fixed at this point in
> time,
Well there's always coming a next release.
> I don't see any benefit in switching back with the next release.
What about
- not unnecessarily diverting from upst
On 13.07.2015 20:26, Christoph Anton Mitterer wrote:
> On Sun, 2015-07-12 at 19:43 +0200, Philipp Huebner wrote:
>> The init script is basically just a wrapper around ejabberdctl, so
>> yes.
> Well that's the point...
>
> As you say the init script is just a wrapper...
>
> So shouldn't we stick w
On Sun, 2015-07-12 at 19:43 +0200, Philipp Huebner wrote:
> The init script is basically just a wrapper around ejabberdctl, so
> yes.
Well that's the point...
As you say the init script is just a wrapper...
So shouldn't we stick with the native upstream name for the config file
(i.e. ejabberdctl.
Package: ejabberd
Version: 15.03-1
Severity: normal
Hi.
I just wondered why ejabberdctl.cfg is moved to /etc/default/ejabberd
(even though there is a symlink).
As per Debian policy
(https://www.debian.org/doc/debian-policy/ch-opersys.html#s-writing-init)
/etc/default is meant for configuration
5 matches
Mail list logo
