On Fri, Jul 31, 2015 at 6:32 PM, Brian Avery <[email protected]> wrote: > Questions: > > 1) What's a section defined as in the About an Image page?
It's the value of the SECTION variable. It's supposed to be some kind of high level classification mechanism for recipes, although I've been told that is not really that meaningful. We show it for all other recipes, though, hence showing it for custom images too. > 2) Why is the license always MIT? This is pretty much what I got from Paul Eggleton this morning, which led to the design as is: All custom images have their license set to MIT. This is because the license applies only to the recipe (.bb) file, and not to the image itself. To see which licenses apply to the image you must check the license manifest generated with each build. You can see this information if you hover over the little question mark next to the license value in http://www.yoctoproject.org/toaster/custom-image-details.html > What if the image they are customizing came from a layer they imported by > hand with their own > LICENSE? Base on the explanation above, it's probably not such a big issue, since the license of the .bb file is pretty meaningless: what really matters are the licenses of the image contents, which are reported by the license manifest. We could inherit the LICENSE of the base image recipe, although I am not even sure if that would be the right thing to do. Paul might have some thoughts on this. > 3) When you download the recipe file do you get the image recipe or > the image recipe and the meta-custom-images layer? Only the .bb file > e.g. how easy is it > to drop your custom image into bitbake and make your new image by > hand... I guess you would need to save the .bb file you downloaded into a custom layer, edit the bblayers.conf file and do bitbake my-custom-recipe. You can also import your custom layer into Toaster and build it from there, although to avoid unexpected behaviour we are going to do some kind of trick with the layer priorities, probably combined with enforcing unique names for custom images inside Toaster. Still ironing out the details of this case. > 4) Do all the custom images go into the meta-custom-images layer? They go into the meta-custom-images layer for the project within which you created them. > What about for different projects? Each project has its own meta-custom-images layer > 5) Does the meta-custom-images layer show up on the layer list for the > project? Yes. You can see it here http://www.yoctoproject.org/toaster/project-configuration.html After some discussion, and since we expose the build system constructs to users, we concluded it is probably better to be transparent and show that, like any other recipes, custom images are also provided by a layer. > Can you remove it? No > What's the behaviour if you do remove it? You can't. All these details will go into a separate design document that covers how custom images are created. Will be working on that next week. Cheers Belén > > -b > > On Fri, Jul 31, 2015 at 7:23 AM, Barros Pena, Belen > <[email protected]> wrote: >> I've opened Bugzilla features to track the front end implementation of 2 >> of the new pages we need for image customisation: >> >> 1. New custom image, where you start the process of creating a new image >> >> https://bugzilla.yoctoproject.org/show_bug.cgi?id=8081 >> >> 2. Custom image details, where you add and remove packages to / from >> custom images >> >> https://bugzilla.yoctoproject.org/show_bug.cgi?id=8082 >> >> Design documentation attached to the Bugzilla entries as usual. Any >> comments, please let me know. >> >> Thanks, >> >> Belén >> >> -- >> _______________________________________________ >> toaster mailing list >> [email protected] >> https://lists.yoctoproject.org/listinfo/toaster > -- > _______________________________________________ > toaster mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/toaster -- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
