I found this interesting concept but would like to explore it more. These are the only links I could find on it. Are there any search terms that cover this topic better?

http://ajaya.name/?p=6353

http://www.nordugrid.org/documents/r...everybody.html

I'm not sure what more there is to explore, the second link is quite comprehensive. Do you have specific questions ?

1 members found this post helpful.

I have not tried to do anything with a Private Rpm Data Base yet but the two guides set it up in the same (home) directory but with different paths.


A few concerns on this topic are:

-How does a Private db use Dependencies in the Main db?

-If the Rpm is a GUI how does the Desktop Environment launch it?

-Not as important but is there a way to implement Yum with the Private db?



The basis for my confusion is that I don't have a technical understanding of


-BASH Environmental Variables

-Chroot : Are these two just permission/Directory Tree Issues?




-Why Rpms would not be relocatable

-Why there is not BASH commands to Relocate a Non-Relocatable Rpm?

-How does a Private db use Dependencies in the Main db?
It doesn't, thats why they use '--nodeps'
-If the Rpm is a GUI how does the Desktop Environment launch it?
If you mean using the graphical package management tools, they won't connect to your rpm database unless you hack them about, even then your changes would be lost on every update
-Not as important but is there a way to implement Yum with the Private db?
yum is a front end to rpm, I don't believe there's any way to point it at a custom rpmdb

The basis for my confusion is that I don't have a technical understanding of


-BASH Environmental Variables
Environment variables have many uses, commonly to pass information to applications and affect the way they behave. They can be set permanently in many places or temporarily. Take a look at /etc/bashrc and for a bucketload of reading 'man bash' (also see the bash builtin command 'export')
-Chroot : Are these two just permission/Directory Tree Issues?
A process can be given an abritrary root, a place it assumes there is nothing above. Chrooting a process is the act of setting it's root to some location to confine it to a part of the filesystem, therefore hiding the rest of the filesystem from it. Search for "chroot jail" for more info



-Why Rpms would not be relocatable
Generally we follow the FHS for placing files, putting them in non-standard places is more the exception than the rule so relocation information generally won't be present
-Why there is not BASH commands to Relocate a Non-Relocatable Rpm?
You can sort of relocate a non-relocatable rpm by using 'rpm .... --root <path>', also if you were in a chroot jail you would be relocated

2 members found this post helpful.

I have been playing with the private DB creation. The --initdb does not create all of the files that exist in a real DB. For example the Basenames, Conflictname, Dirnames, etc... do not get created. I have to copy these from an actual RPM database. Even when I do this the "rpm -ivh " command returns a "permission denied" message on my private DB.

What's the correct way to get these files without having to perform a copy?

1 members found this post helpful.