[bundleXpcf/bundle] Accept multiple configuration files/packagedependency files

[jim-bcom]

CONTEXT

• Say we want to split the project configuration into several files (e.g. one for modules and one for properties in order to be able to test different values for the components properties).
• We could also have several packagedepedencies files to have fine grain control
• We also could want to bundle several executable/projects together.

PROBLEM

• Currently remaken bundleXpcf only take one parameter for configuration file and one parameter for packagedependencies file.
• So in the context described above, it requires to build multiple calls to remaken install on several configuration files, by passing or not the pkgdep files in order to avoid the duplication of work, etc... Or make calls to bundleXpcf for config files and bundle for properties files...

SUGGESTED SOLUTION

• It could bring some confort to be able to pass all the configuration and pkgdeps files on the same call to remaken bundleXpcf.

[jim-bcom]

You asked me offline a case where this could be useful compared to calling bundleXpcf several times with different files.

Here's an example:

• We have an executable projet that depends on an XPCF component from another module.
• We have split the configuration files into modules/properties for each project.
• So we need to pass several configuration files to bundleXpcf (only the modules ones I guess...?)
• Currently, as remaken bundleXpcf does only take 1 pkgdeps file (mandatory) and 1 config file, we must call

remaken bundleXpcf --pkgdeps pkgdeps.txt configExecModules.xml
remaken bundleXpcf --pkgdeps pkgdeps.txt configDepModules.xml

PROBLEM

• As pkgdeps file is mandatory (as seen in other issues), we must pass it everytime. This results in unecessay work.
• Maybe the 2 config files could share some components, so again, unecessary work is done

SUGGESTED SOLUTION
By making possible to perform only one call:

remaken bundleXpcf --pkgdeps pkgdeps.txt --pkgdeps pkgdepsSpecific.txt configExecModules.xml configDepModules.xml

• We can keep the pkgdeps file option being mandatory (as decided in other issues), and avoid passing empty pkgdeps on the second call as a lame optimization.
• we can potentially benefit from the ability to merge the configuration files to avoir unecessary work.
• Adding the ability to specify several packagedependencies could also add some flexibility, and allows for some new workflows.
• use one liners in scripts.