Description of problem: I don't know Japanese so I went ahead to erase libkkc & friends but found strange dependencies for installing & erasing packages. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: 1} yum install libkkc - Install Dependencies - libkkc-common , libkkc-data 2} yum erase libkkc - Erase Dependencies - None - leaves dependent libkkc-common , libkkc-data on the system 3} yum install libkkc-data - Install Dependencies - None - keeps it unusable without libkkc 4} yum install libkkc-common - Install Dependencies - None - rpm -qi libkkc-common - The libkkc-common package contains the arch-independent data that libkkc uses at run time. These are just some examples but my intention of pointing it out was that such packaging can either install partial unusable packages or leave dependent packages, cluttering the system either way.
Sorry, could you elaborate a bit on what you are suggesting? Do you mean the libkkc package should contain the contents of libkkc-common and libkkc-data? Or, libkkc-common and libkkc-data should depend on libkkc? Neither seems feasible to me, and I see other packages do similar packaging, for example emacs and emacs-common.