[oe] packages versioning
Mark Hatle
mark.hatle at windriver.com
Fri Dec 9 16:15:13 UTC 2011
On 12/9/11 9:59 AM, Mr Dash Four wrote:
>
>>> One more query regarding this - how do I remove
>>> packages I do not want included in the final image? Is there a way to do
>>> that (fairly) easily?
>>>
>>
>> Yes, create your own image recipe.
>>
> I was hoping that there is an easier option ("(fairly) easily" being the
> keywords here)!
>
> I tried to trace where these packages are derived from, but could not
> find anything. For example, I'd like to remove ash (and possibly the
> whole BusyBox setup) and replace it with bash and their package
> equivalents. By looking at the tasks/ as well as images/ directories I
> couldn't find where these packages are derived from, hence the above
> question.
The creation of the filesystem image is driven by a number of components.
Basically it works like this:
You select an image to build. The image sets a few flags and a basic set of
requirements. The image inherits the core-image.bbclass.
The core-image.bbclass uses the flags, machine settings and extra settings to
determine a list of actual dependencies. Most of these dependencies are broken
into groups. Some of the groups are individual sets of recipes, while most are
actually tasks.
The tasks themselves are broken down into functional areas. These functional
areas are designed to give you control at a "functional" level, designed to
assist people who really aren't sure exactly what source packages to start from.
If you look for a list of the tasks you can see the breakdown and components.
In the recipes-extended, there is a set of core-tasks. These tasks allow you to
build up a system starting with busybox, and slowly add to it and replace
busybox with the discrete components from util-linux, coreutils, etc.
I have a spreadsheet (OpenOffice 17k, or Excel 81k) that lists all of the
current breakdowns. If you are interested send me an email off list.
--Mark
More information about the Openembedded-devel
mailing list