[ https://issues.jboss.org/browse/JBDS-4537?page=com.atlassian.jira.plugin.... ] Mat Booth commented on JBDS-4537: --------------------------------- Oof, open can of terminology worms incoming.... :-) It's because in koji "package" is a bit closer in meaning to "specfile+source" so here you are searching what effectively the list of source RPMs (build input) rather than the list of resulting binary RPMs (build output). The relationship between source and binary RPMs can be 1 to many. In the simplest case, the resulting binary RPM implicitly has the same name as the source RPM. You may also have additional declarations in the spec file defining additional binary RPMs with different names -- it's a good way to separately package logically discrete or optional features of a software using a single specfile. I am aware that I am using "package" to describe a binary RPM named for its source RPM and "sub-package" to describe binary RPMs that are named differently to the source RPM. Sorry about that -- overloaded terminology strikes again! Really, all binary RPMs are equal in the eyes of the gods, and you can only not install it by itself in the normal sense that it may have dependencies on other RPMs. Does that make sense? -- This message was sent by Atlassian JIRA (v7.2.3#72005)