Question regarding RPM packaging of interactive software.
thinklinux.ssh at gmail.com
Sun Jan 9 18:37:12 UTC 2011
> My understanding was that we never touch databases in RPMs, period. We
> don't create, modify, update, or remove. I can't recall at the moment
> where this stems from, but the rationale, as I recall, was that we can
> never be sure if the database is available at RPM install/upgrade time.
> Plus, the consquences of a failed or interrupted RPM transaction on the DB
> could be. . interesting.
> So, in short, don't do it, and but if no one can find a citation in the
> guidelines someone ought to write a draft, for that way lies madness. :)
Thanks for your help.
I shall take these to upstream.
More information about the devel