Hi Jessica, Thanks so much for considering my feedback :-) I do tend to be "wordy", don't I? :-)
On Fri, Aug 10, 2012 at 6:56 PM, Zhang, Jessica <jessica.zh...@intel.com> wrote: > Am I missing any point that you're also trying to make here? No, I think you've captured everything quite succinctly. Expanding on point 1 a little bit: > 1. hob should save the customization into the project's configuration, > instead of using its own configuration saving mechanism. In this way, people > will be able to achieve same customized build result from command line or > using hob. Due to the fact you have to be "in a project build" (i.e. you have to have already sourced oe-init-build-env) in order to run Hob I thought the configurations I was performing in Hob were changing the configurations of the project from which Hob was started. So I was really confused that I couldn't find any of the changes anywhere. But what is even more confusing is that when Hob starts it begins by taking your project's base configuration. I feel Hob sort of "sits on the fence" in the way it starts with the project's configuration, but then doesn't update it (back again) as it goes along. Since I was hoping to use Hob, and then look through the project's configuration to see how my Hob changes were changing the underlying configuration files I was getting a bit of a run-around since none of the changes from Hob were showing up anywhere I could find. If someone wanted to say "Hob is independent of the project from which it is started" I would be okay with that, but in that case Hob shouldn't start with the given project's configuration and shouldn't need to be run after sourcing a particular project's oe-init-build-env file. In fact I was originally going to send an email asking where Hob's configuration changes were being saved until I started playing with the "save as template" thing. With respect to number 2: > 2. Current "Save template" wording is confusing. On the one hand I would prefer to be able to save the configuration as I go along. It looks like the only time I can save a given configuration is after I have successfully built an image (?). Perhaps I take a long time to sift through the available packages, maybe I don't complete that all in one step. So I'd like to be able to save as I go along. Then, after building my packages, perhaps I then take more time to sift through the build artifacts to determine which I want in my image. Again this step can take quite a while and I'd prefer to be able to save intermediate configurations as I go along (just in case of a crash or whatever). On the other hand I can't help think that if Hob could be saving the configuration to the current project's configuration files as I go along then having an explicit "save template/configuration" wouldn't even be required. If one instance of Hob is meant to work with only one given project then what to save and where to save it would become explicit, so perhaps Hob could just save with every click as I go along? > I think these are valid points, could you file enhancement bugs for them in > Yocto project bugzilla for us to track them and plan the future work for them > accordingly? Yes, thank you. _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
