Oh and of course, it *is* all very very different from what user/group handling
in rpm has traditionally been. You need to just unlearn that all :smile:
The key difference really is that with the sysuser integration, the rpm running
the transaction is what does the work and contains any tooling dependencies,
whereas in the traditional model it's the packageset being installed that get
to do the work. So instead of adding more shadow-utils deps and the like, you
instead get to *remove* those deps from the packages. And, like said, you can
now have arbitrary users starting from the very first package being installed
because the user/group tooling doesn't need to be bootstrapped first in that
environment.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2697#issuecomment-1750666169
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2697/1750666...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
