From: Joseph Hickman <joseph.e.hickman@gm...> - 2011-10-21 13:02:06
I built my own image, based off the minimal. I added packages to the bitbake
recipe as needed. I now see several files in /usr/lib/opkg/info/ contain the
path the rootfs was compiled in. These paths are not valid for the gumstix.
For example, I see in task-boot.control:
And in kernel-module-iptable-nat.postinst:
arm-angstrom-linux-gnueabi-depmod-2.6 -A -b $D -F
My questions about the *.control files: Are they necessary? Can I delete it
and have things still work? Is the "Source:" field just a comment I can
My questions about the *.postinst scripts: Are they necessary, too, or can
they be deleted? I don't know much about how opkg works. I've found
descriptions that say the *.postinst scripts that are run after
installation. Is "installation" referring to the initial addition to the
system, or are packages "installed" each time the system boots?
Should I have added these packages to the image in another way that would
have removed these files or fixed the paths they point to?
View this message in context: http://old.nabble.com/okpg-files-in-rootfs-contain-compilation-paths-tp32696117p32696117.html
Sent from the Gumstix mailing list archive at Nabble.com.
Get latest updates about Open Source Projects, Conferences and News.