[ProFTP] (New) Modules zu activate

Hilmar Preuße hille42 at web.de
Sun Nov 18 21:54:27 GMT 2018


On 13.09.18 10:00, Francesco P. Lovergine wrote:
> On Thu, Sep 13, 2018 at 08:05:49AM +0200, Hilmar Preuße wrote:

Hi Francesco,

Sorry, late response!

>> In case of upgrades the config files are never replaced, if already
>> present, which does not make sense to me.
>> Why don't we install the config files into etc from the beginning and
>> leave the handling of them to the normal Debian mechanisms?
>>
> 
> The obvious reason is allowing a pre-editing of the existing file
> just to fix minor changes due from time to time which could be managed
> in automatic way. The 'normal' configuration handling leaves also
> those minor changes to the maintainer. Or - which is the same - we
> should 'simply' provide a template for configuration files and ignore
> any other things.> The other approach is more flexible. E.g. in the past some options
> changed simply names and could be NOT present in the template but
> present in the maintainer script. The current approach does allow to
> fix those silly changes without bothering the poor maintainers. Makes
> sense?
> 
To be honest, I don't understand your explanation.

Currently we have the situation that the proftpd.conf is never
overwritten, if it already exists. So even if we provide a new config
file; it is not delivered to the end user.

Regarding the current state of the git: IMHO it is in a good state to
release -3 to get rid of our RC bug. If you think we should revert
adc12897, feel free to do so.

H.

-- 
sigfault
#206401 http://counter.li.org



More information about the Pkg-proftpd-maintainers mailing list