It also occurs to me that a source for the confusion might be that there is more than one build process going on with BitBake. It is used both to create packages and to install them into a rootfs in order to create an image. Thus, the workflow looks something like this, starting from the point of download:
[tarball/repo] -> [source] -> [binary] -> [package] -> [image] or, the evolution of a chunk of information, in terms of its file type: [.tar.gz/.git] -> [*.c,*.h,Makefile,etc] -> [executable] -> [.rpm,.deb,.ipk] -> [.ext3] Yes, this is a gross generalization with many exceptions. I'm just trying to capture discrete terms for each step of the process. Our term "package" is often used to describe the first item, sometimes to describe the second item, and always used to describe the fourth item. It is also sometimes used to describe the repository - the ecosystem of files that defines a given piece of software. Brian - thanks very much for starting this conversation. Terminology is important, and just because people use overloaded terms every day doesn't mean we shouldn't work to differentiate them. -- 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
