Currently the upstream packages in Fedora provide the following virtual packages:
qpid-cpp-client -> qpid(client) qpid-cpp-client-devel -> qpid(client-devel) qpid-cpp-client-rdma -> qpid(client-rdma) qpid-cpp-server -> qpid(server) qpid-cpp-server-ssl -> qpid(server-ssl) qpid-cpp-server-ha -> qpid(server-ha) qpid-cpp-server-rdma -> qpid(server-rdma) qpid-cpp-server-xml -> qpid(server-xml) qpid-cpp-server-store -> qpid(server-store) Justin pointed out that this doesn't provide enough detail and may cause problems in future if and when a new client API, for example, is provided. So, I'm looking for some ideas on better virtual package names to be provided. For example, the qpid-cpp-client API is qpid::messaging, so this virtual package could be better named: qpid(messaging) In the same way the qpid-cpp-server virtual package would be: qpid(broker) or: qpid(qpidd) The other packages should have names that fall in line with those base names; i.e., messaging-devel or broker-ha. Ideas or thoughts? -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
pgpLTXBVutB0S.pgp
Description: PGP signature
