On Sat, Feb 06, 2021 at 10:10:23AM +0100, Marc Haber wrote:
> On Thu, Feb 04, 2021 at 04:08:22PM -0600, Corey Minyard wrote:
> > On Thu, Feb 04, 2021 at 09:10:40AM -0300, Antonio Terceiro wrote:
> > > Beyond adding an NEWS entry, another easy thing you could do is
> > > replacing the current command in ExecStart= by a wrapper script that
> > > uses ser2net.conf if it exists (while printing a big fat warning), and
> > > ser2net.yaml otherwise.
> > 
> > This is how ser2net currently works.  It will load ser2net.yaml if it
> > exists.  If it does not, it will load ser2net.conf.
> 
> But the package brings a ser2net.yaml with it, so ser2net.conf wouldn't
> be read in any case.
> 
> > Writing a converter wouldn't be too hard, I should have done that.
> > There is some trickiness dealing with colons in device names, but I
> > think that's the only hard thing.  If you don't do this, I can do it.
> 
> Considering ser2net is a not widely used package, targeted at advanced
> users, I think that displaying information about the configuration file
> change (which I forgot in the last upload) would probably be the easiest
> way to go ahead and get ahead of the pending freeze.

Yeah sure. Users will have to deal with this at some point in any case,
as I expect that the old format won't stay around forever.

Thanks both of you for your time.

Attachment: signature.asc
Description: PGP signature

Reply via email to