On Thu, Mar 6, 2014 at 11:03 AM, Daniel J Walsh <dwalsh at redhat.com> wrote: >> >> All in the world, or all that have been created for currently installed >> packages? Is this as bad as rpm packaging where any two different sources >> are likely to conflict in name and/or contents? >> > Well we have not had this problem over the years, since most people upstream > their policy. Right now if a customer installed a policy file which > conflicted with the base policy, it will get overwritten. I guess if they did > it will rpm then it would get you an RPM error/warning. What does 'upstream' mean in the context of packages that aren't included in RHEL base or EPEL? It just seems like a giant list of global variables without any structure or namespace management. -- Les Mikesell lesmikesell at gmail.com