Speaking ex cathedra (as an ex tech writer) I'd say either Included or Installed would work, but the proper term would depend on when this table is shown.
Included = included in the build, so it's a pre-build term. Installed = installed in the rootfs, so it's a post-build term. Deployed = installed onto the target - not appropriate for this list, I think. As Jason says, packages can be built that are never inserted into the rootfs, so if this is a list of all packages in the build, I'd stick with Included. On Tue, Jul 9, 2013 at 10:29 AM, Barros Pena, Belen <[email protected]> wrote: > > > On 08/07/2013 18:13, "Jason Wessel" <[email protected]> wrote: > >>On 07/08/2013 11:09 AM, Barros Pena, Belen wrote: >>> I am looking at the table of packages that will be part of Web Hob. That >>> table will list all packages built during a certain build. >> >>What table are you making a reference to? I didn't see a pointer in the >>e-mail. > > You didn't see it because there wasn't one: my bad. Here is a rough sketch > of the kind of table we are thinking of: > > http://belenbarrospena.github.io/web-hob-1.5/all-packages-size.html > > By the way, when I said: "I am looking at ..." what I meant was "I am > working on the design specification for the packages table that will be > part of Web Hob". Sorry for the vagueness. > >> >>> >>> Not all the packages in that table ended up in the final image. To >>> differentiate them, there will be a column that will tell you if a >>>package >>> is in the final image or isn't. How should that column be called: >>> Deployed? Included? Something else? >> >>There is a distinct possibility that the number of packages built to >>support the webhob that go on the final target image is zero, >>particularly in the case that you just need a particular configuration of >>busybox + a kernel. >> >>Without seeing your table it is hard to say, but generally we have >>nativesdk, native, cross and target packages. >>I would have imagined you can just specify if something is in the target >>image or not. >>There certainly are target packages that get built but not installed to >>the image, and for these we just use the term installed to sysroot vs >>installed to image. > > So, if I understand correctly, you are suggesting "installed" (to image), > instead of "included" or "deployed". Is that correct? > >> >>Jason. >> > > --------------------------------------------------------------------- > Intel Corporation (UK) Limited > Registered No. 1134945 (England) > Registered Office: Pipers Way, Swindon SN3 1RJ > VAT No: 860 2173 47 > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > > _______________________________________________ > webhob mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/webhob -- Jeff Osier-Mixon http://jefro.net/blog Yocto Project Community Manager @Intel http://yoctoproject.org _______________________________________________ webhob mailing list [email protected] https://lists.yoctoproject.org/listinfo/webhob
