Quote:
Originally Posted by arm74
Cool!
obviously I'm loosing the dependency check too, can you confirm?
|
Sure ! But you asked for the way to do it without creating rpmdb.
dependencies tracked via rpmdb, so...
Quote:
last hope: someone know if the problem can be handle yum side?
In other words, can the simple user run successfully yum install giving it as parameter the rpm relocation path?
Thanks a lot, Arm
|
Lets get it straight.
There are different reasons why rpm install should be run as root.
Some of them can be worked around, another - can't
1) rpm should put files in the directories where only root has write permissions.
Workaround - relocation path
2) rpm have write to rpmdb. Only root has access to rpmdb
Workaround - specify your own rpmdb with --dbpath
3) Sometimes pre/post install script have to do something only root allowed to do. for example creating new user.
Workaround - run rpm with --noscript option.
4) Sometimes program should have specific owner in order to work.
For example su, sudo, login have to be owned by root and with permission 4755 (root setuid programs)
No workaround
So while (most of) rpms can be installed as regular user to alternative location with alternative rpmdb, why bother ?
You lost most/all of rpm benefits.
In install by regular user case
rpm2cpio looks to me like more cleaner solution