I think it would be very useful for debugging user
problems if the sfcb install process creates a usable,
if empty, working root/cimv2 repository. Specifically,
copy stage/default.reg to registration/providerRegister
and then mkdir registration/repository/root/cimv2 (and
maybe touch ./classSchemas in the latter, though this
is not strictly necessary).
This would allow a new user to download and install
**just** the sfcb package (and perhaps wbemcli) and
immediately be able to determine whether the thing is
working or not, by doing an enumerateclass operation. eg
wbemcli -dx ec 'http://localhost:5988/root/cimv2'
Although this wont return any class info, it will show
that the sfcb is receiving and processing requests, and
sending back XML. Having a baseline such as this to
show the sfcb is 'up' would be very useful for
debugging purposes, before installing any of the other
packages that may introduce other problems, corrupt the
Whereas currently a user must also download the CIM
schema, mofc, cmpi-devel, indication-helper, cmpi-base
packages, build and install them before having a
working repository to run a query against.
Currently sfcb install creates neither the
providerRegister file nor the repository dir.