Adapting kcfg.xsd to match support for dynamic config file names

[Tobias Koenig]

Hej,

kcfg.xsd has the following entry:

 <xsd:element name="kcfgfile">
  ...
 </xsd:element>

which means that every .kcfg file must contain an entry for the
configuration file it shall write to.

However there are several use cases where it is not possible to
provide these information. In Akonadi for example we have the resources which
are applications that are started with an unique identifier as argument
and this identifier is used to create the application name that is passed
as 3rd argument to KCmdLineArgs::init(). So every resource has its own
configuration file, depending on its application name.
Of course these information are not available at compile time, only at runtime,
so require the config file name in the .kcfg file doesn't make sense here.

If no 'kcfgfile' is given, kconfigxt falls back to the default config file
<appname>rc anyway, so can we change the .xsd file and add 'minOccurs=0' to this
entry to make it optional?

Ciao,
Tobias
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20100125/67ed8afb/attachment.sig>