Manual step in upgrade process for a FSWC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



I intend to switch pam_userdb's database provider from BerkeleyDB to GDBM and I'm writing a Fedora System-Wide Change for Fedora 40. The upgrade process would involve a manual procedure where the user needs to run a conversion tool for the database. Is this acceptable?

An automation process could be created, but the location of the database is configurable, which increases its complexity and effort. Especially for a PAM module that is not widely used. Another option I can think of is to automate the conversion process for the default location, and leave the manual conversion for those using a tuned location. Would that be acceptable?


Iker Pedrosa

Senior Software Engineer, Identity Management team

Red Hat

Txapela (gorria) buruan eta ibili munduan

(Red) hat on his head and walk the world

Basque proverb   

devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam, report it:

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux