Shane Voss wrote:
let's say I want to install all of my packages in /opt2. Will the first
> RPM I install be considered the owner of the /opt2 directory?
Packages can own entire directories, or some or all of the files within them.
It is easy to carelessly give too wide a scope, and you will then get conflicts.
See: http://tldp.org/HOWTO/RPM-HOWTO/build.html#FILES
Shane
My advice would to just list the files unless the directory is really
specific for one rpm.
So just list
/opt2/bin/mybinary
/opt2/lib/mylibrary
and let rpm deal with creating the directories for your programs.
I guess the exception to that is if there is a directory that you want
to have specific permissions. If that is the case, then you should list
it, giving it the permissions that you want.
Troy
--
__________________________________________________
Troy Dawson [email protected] (630)840-6468
Fermilab ComputingDivision/LCSI/CSI DSS Group
__________________________________________________
