On to, 14 huhti 2022, Matthew Miller wrote:
On Wed, Apr 13, 2022 at 07:47:23AM +0300, Alexander Bokovoy wrote:
> >I think that if the Samba package config file is unmodified, the tool should
> >replace that unmodified config file with one that just has this minimal
> >config pointing to the registry (along with a suitable comment). If, on the
> >other hand, the config is non-default, the tool should warn and _offer_ to
> >do that, noting that it will replace existing configuration (and of course,
> >it should make a backup).
>
> Please do not do that unconditionally. As I said already first time we
> discussed this topic, use of the registry is not compatible with several
> Samba modes and should not be done automatically. Even if user has
> installed a cockpit plugin, it does not mean that configuration has to
> be changed.
I'm not suggesting doing it unconditionally, but I think it should be done
with as little bothering-the-user as possible _when the samba package is
installed via the plugin._ And I'd like it to be that easy in other cases as
well. A wizard that walks people through what you're saying are possibly
complicated and dangerous steps doesn't seem like good UX for the user
profiles we've identified for Fedora Server.
I do not see how you can detect whether Samba package was installed via
the plugin. Can you please provide more details on how you plan to
provide that?
I don't want you to create a big wizard. I think we both agree the App
should detect whether current configuration is supported or could be
supported and that be it.
--
/ Alexander Bokovoy