On 23 January 2017 at 15:37, Thorsten Kukuk <kukuk(a)suse.de> wrote:
On Mon, Jan 23, Jan Engelhardt wrote:
I do not see the issue yet - the subvolume
mounted as /opt ought to have
the same hierarchy level as /usr and /var so that it gets included in
snapshots (read: if it does not, it better should).
/opt is for ISVs and they can write user data there, like databases.
You don't want to loose changes to that data during rollback.
But doesn't the status quo mean you can have a situation where the RPM
database and the reality of /opt are two very different things?
Theoretical Case in point, something like Oracle DB, which users rpms
User installs Oracle DB rpms which produce /opt/oracle and starts
using the database
User then rollsback to a period before the installation (for whatever reason)
/opt/oracle is preserved, the binaries and data are all still there;
This is a good thing, no arguments there.
But now rpmdb would have absolutely no record of the Oracle DB rpm
How would a user be expected to uninstall the Oracle DB rpm in this case?
(I realise this is straying OT as the problem is present with the
status quo and not made any better or worse with Transactional
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org