When the target system does have package management enabled, some users may prefer to actually interact with it rather than write files directly. This introduces a number of complexities: * We need to know up-front that we are going to deploy via the package manager so we can actually build the packages at "devtool build" time. Within the extensible SDK this is probably something that would be set via the config file. * Do we install all packages produced by the recipe? Probably yes, but that will likely drag in a lot of dependencies * We need to ensure do_package_qa doesn't unduly get in the way considering we may not care about certain warning/error situations in this context * We must ensure all files get packaged somehow or they can't end up on the target * This must of course work with all three of the package management backends we support * We need to ensure our version really does get installed and isn't skipped because the version isn't greater than any installed version; then the question is do we force or just ensure it really is greater?
Hi Paul, Isn't it enough to just build out the package using devtool? When the user has the package (e.g. .rpm file), it's pretty convenient for him to do something with it. For example, copying the rpm file onto the target and install it via package manager (rpm or smart, etc) is easy. So I think we don't need to automatically install/uninstall the package for the user, we just build it out. What do you think? Best Regards, Chen Qi
The point with this is to have a one-step deployment tool that definitely deploys the executables to the target (with all of its dependencies, should they not already be installed). You say installing the package is then easy - but if there are any dependencies, or the version number hasn't increased, it starts getting a bit more difficult. Sure, the user can then set up a web server to share the feed, add the package feed on the client side and then install it - but that's something they have to know how to do.
(In reply to comment #2) > The point with this is to have a one-step deployment tool that definitely > deploys the executables to the target (with all of its dependencies, should > they not already be installed). You say installing the package is then easy > - but if there are any dependencies, or the version number hasn't increased, > it starts getting a bit more difficult. Sure, the user can then set up a web > server to share the feed, add the package feed on the client side and then > install it - but that's something they have to know how to do. Got it~ Thanks for your detailed explanation. Regards, Chen Qi
A valid idea but the complexity of the feature is somewhat a duplication of an existing devtool feature and we don't have anyone to work on it.