I haven’t used recent versions of this tool, but I have found it essential to be able to modify the image before the final package is created. There is no way that this tool can anticipate all of the custom configuration that might be needed, and I do not want to duplicate its ability to create an image and to build a package from the image.
> On Jun 5, 2019, at 2:16 PM, mark.reinh...@oracle.com wrote: > > - It’s not clear why there are distinct subcommands to create an image > vs. to create an OS-specific package. Given the name of the tool, > I’d expect creating a package to be the primary behavior. An option > to preserve the image, which is just a temporary result, could make > sense, as well as another option to skip the creation of the > package, but I don’t understand the need for subcommands.
