(sorry I don't have the original email around to which to reply...) For the past many years I have been accumulating various scripts which I have used to create the root filesystems for various embedded systems. These scripts create updates, generate artifacts for creating bootable CF cards, and produce complete VMDK images in one VMDK file. This script allows the user on the cmdline to specify things such as the size, number, and filesystem for a flexible number of partitions. These scripts work on systems that are both 8 years old, as well as the latest distributions, they work with systems that have a little memory, to ones with lots. They can use any of lilo, extlinux, or u-boot (specified on the cmdline).
I want to begin integrating this work with OE/YP in order to provide a demonstration so others can evaluate it and decide if this is something along the lines of what they'd find useful. http://lists.linuxtogo.org/pipermail/openembedded-core/2012-June/023484.html http://lists.linuxtogo.org/pipermail/openembedded-core/2012-July/026938.html Although I'm quite familiar with my scripts... with OE/YP, not so much. So I was hoping to find some pointers for how I might proceed with this integration. Currently my scripts still require various privileges. So in the same way that a build runs to completion and then the user might run "runqemu" from the poky/scripts directory (and be required to give the root user's password to setup the tap networking), I would like to create a script in poky/scripts that would be run after a successful build which also might require root's password. I would like to ignore any images that are created as part of the build and rely solely on a package feed. So, provided a package feed is available, what would be the easiest way, in a shell script (run after a successful build), to say: "populate this random (specified) <directory> with all the packages the user wishes in their image". In other words I don't want to have to care whether the user has selected RPM or DEB, or IPK, and (preferably) I don't want to have to care what packages the user has selected (through various means) to be installed. I want to setup and create <directory> beforehand, I want OE/YP to populate it (without deleting <directory> or changing it in any way other than to populate it), then I want OE/YP to leave it alone for me to post-process. Is that possible? I was thinking that, as a kludge, I could use bitbake-env if I needed to get bitbake variables into the script. Any suggestions? _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core