Re: config file name and format change
On Thu, Feb 04, 2021 at 10:37:18PM +0100, Christoph Biedl wrote:
> Marc Haber wrote...
> > My idea would be to have two distinct systemd units, ser2net and
> > ser2net-oldconfig, with appropriate ConditionPathExists directives.
>
> From my experience, that is a bad idea. While being easier right now,
> this results in having to maintain two flavours for ... possibly
> forever.
until Upstream removes support for the old format, displaying a big fat
warning whenever the service is started with the old format config file.
> So I advise to provide an upgrade path for all users even if this means
> work for you as the package maintainer. Still in my experience it's
> better if the maintainer spends time on a sound automated solution
> than leaving figuring out the gory details to the users. For me, this
> is also an implication of the Social Contract ("guided by the needs
> of our users").
While you're theoretically right, I would do that for an high popcon
package, but not for a package with under 200 registrations in popcon.
> As a last resort: The old format is extremely simple, the new one is not
> that complicated. It seems feasible to do the conversion with a few
> lines of awk, so it could be done in preinst. Also, that method could
> even preserve any comments.
It would also need testing and is likely to introduce bugs right before
the freeze.
> All this is more work than some alert boxes or a paragraph in
> README.Debian. But I think it's worth it.
Sadly, I have to disagree. There is no time at the moment.
> Christoph, ser2net user since 2004
Thanks for your comments, and for using ser2net!
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Reply to: