| Hi 1. Does anyone have any suggestions for package naming? Some packages will be ok, but others not. For instance, we have a watchdog package. If I call it "dog" there is a high chance ther may be some other package named "dog" installed on a system that this one would also go on, and there could be a conflict. It could be a completely different independent watch dog program. I know Java packages have the company name and all that in reverse, like com.mcdonalds.hamburger.utils or whatever (that name is just an example). Should packages be named similarly, like com-mcdonalds-hamburger-utils-1.0.0.rpm in case there are other packages named util? 2. I have been giving my packages group names (like in the examples Applications/Databases). You can do an rpm query like rpm -q -g Applications/Databases to find rpms with that group. Now say you have a company called "foo" and you give your groups names such as foo/bar, foo/pub, foo/tavern. You want to find all the groups with foo. rpm -q -g foo/* does not work. Nor does rpm -q -g foo. Is there any way to do this? (other than rpm -qa --queryformat '%{NAME}-%{VERSION}\t%{GROUP}\n' | grep -i foo |