https://bugzilla.novell.com/show_bug.cgi?id=801920 https://bugzilla.novell.com/show_bug.cgi?id=801920#c17 --- Comment #17 from Yarny Yarny <Yarny@public-files.de> 2013-04-21 11:39:57 UTC --- Thanks for your feedback Robert.
Rather than __generate... you want to implement a __getCmdArgsFromCfgFile method that delivers the arguments as a string. The string usage is more flexible as we can use it in concatenation. I did this to anticipate situations where the Manager-class requires arguments as array of strings instead of a single string --- I figured the transformation into a single string is easier than the reconstruction of the array. If this is never needed, I can certainly create a single string in this method.
There is an issue in the case where the preferences from the user description get merged with the boot image description. In this case the name of the package manager config file will be defined, but the boot image description will not contain the file, thus "tie %cfgini, 'Config::IniFiles', ...." will probably fail in some weird way. There is no protection against this case. I don't see an easy solution to this ... honestly, I don't fully understand the problem. So kiwi "internally" creates another config.xml when the boot image is about to be set up, and this is a mixture of the user-specified config.xml and some other config.xml? Following our current path, we would need to add code which copies the packagemanager-configfile to the place where this intermediate config.xml is stored, I guess. To me, this idea sounds quite fragile.
Would it be easier to move the complete packagemanager configuration into the config.xml itself? We already discussed the idea in Comment #3 and Comment #4 to add something like
<packaManagerOption name=".....">.......</packageManagerOption> But this is probably too package-manager-specific. I'd like to propose two alternatives: I. <packageManagerArguments subcommand="install">--download as-needed --force-resolution</packageManagerArguments> <packageManagerArguments>--verbose</packageManagerArguments> i.e. put the additional command-line argument string between xml tags and use some "subcommand" attribute to determine which string is to be used, or II. <packageManagerConfiguration> [zypper] verbose= [install] download=as-needed force-resolution= </packageManagerConfiguration> i.e. just put the ini-file-content between two xml tags. Would this solve the boot-image-problem? Would it cause other problems which I currenly miss to see?
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.