[ELDK] Just starting - ipkg errors

[Larry Baker]

Wolfgang,

>> Even though a target does not have a package manager installed, it seems
>> to me to be quite useful to have the package database (as long as it is not
>> large).  ...
> 
> That's the problem.  The package database has a substantial memory
> footprint in the root file system, so for small, resource-optimized
> configurations you don;t want to have it / cannot affort it.

This is exactly my concern; I agree completely with your choice.

>>    ...  If this is under the control of DENX, may I suggest this be considered
>> a request item for a future ELDK release?
> 
> Of course you may suggest it - but I see no reason to change the
> current configurations.  If you have ample resources that allow for
> such a big file system image, then just use one of the more full-blown
> configurations - or roll your own meeting exactly your requirements.


May I suggest an alternative: do not include the package database within the rootfs
itself, but do provide it along side the rootfs image.  The rootfs would not quite be
self-documenting.  But, to know exactly what was installed in a rootfs image, you
would not have to know at what commit was the git repository when the rootfs was
created in order to find the Yocto build recipe that created it.  It can also serve as a
validation that I can correctly recreate your rootfs -- both the rootfs images and the
package databases should be the same.  Or, for example, that I have properly
recreated your rootfs with updated packages, such as to apply security patches.

With thanks,

Larry Baker
US Geological Survey
650-329-5608
baker at usgs.gov