<snipped> On Tue, Sep 18, 2012 at 12:04 PM, Trevor Woerner <twoer...@gmail.com> wrote: > On Tue, Sep 18, 2012 at 2:23 PM, Brian Lloyd <bll...@familyhonor.net> wrote: >> Most of my hits for such an item >> discuss the packages I will need to install in my host distribution so I >> can use the yocto project (not surprised, the danger of a term as vague >> as packages). > > In bitbake/yocto/OE/etc. the term "packages" is not vague and has a > very specific meaning: bitbake processes recipes to produce one or > more packages. Some of these packages are then assembled into an
This is quite true - but the term itself is overloaded. I have often heard "package" referred to also as the collection of source code one would use to create a given piece of software, e.g. "the busybox package". This is no doubt the result of downloading numerous "packages" from the net in binary form rather than source. It doesn't help that there are "source packages" in the RPM world (http://www.rpm.org/max-rpm/s1-rpm-miscellania-srpms.html) and in the Debian world (http://www.debian.org/doc/manuals/apt-howto/ch-sourcehandling.en.html), so the confusion is natural. In OE-based systems like the Yocto Project, the term refers to the results of a build rather than the ingredients. I agree with you that we should continue to push the correct usage to unload the term. Anyone have a good term for "source packages"? -- Jeff Osier-Mixon http://jefro.net/blog Yocto Project Community Manager @Intel http://yoctoproject.org _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
