“mixer build bundles” should be able to process a new "content()" keyword in the bundle definition file that specifies a relative/absolute path to the top level content directory. E.g. content(\<dir>)
Once the full chroot is built, the content should be injected into the full chroot after conflict checks. If there are conflicts, then error out. Generate the bundle info files from the final chroot as usual.
“mixer build bundles” should be able to process a new "content()" keyword in the bundle definition file that specifies a relative/absolute path to the top level content directory. E.g. content(\<dir>)
Once the full chroot is built, the content should be injected into the full chroot after conflict checks. If there are conflicts, then error out. Generate the bundle info files from the final chroot as usual.