[OE-core] [Draft design][RFC] Running postinst at rootfs generation time

[Tom Parkin]

I'm interested to read about this initiative as we've recently
stumbled over the issue of postinst scripts in trying to port our
build to OE.

So far it seems the primary concern is about the boot-time impact of
postinst on the target.  But for the use-cases I'm interested in, we
need to capture all install processes as a part of the build in order
to output a fully-provisioned read-only rootfs image (e.g. squashfs).
Our boxes don't typically modify their filesystems at runtime, other
than to take full updates (completely new rootfs images).

I think the reduction, or even elimination, of target-run postinst
scripts would help a lot with the read-only rootfs case.

Tom

On 4 July 2011 01:23, Cui, Dexuan <dexuan.cui at intel.com> wrote:
> Hauser, Wolfgang (external) wrote:
>> Beside the discussed changes, the postinst scripts should be executed
>> in the dependency order.
>> At the time, the scripts are executed in alphabetic order, which
>> breaks the image generation if depended packages are not in
>> alphabetic order.
>>
>> e.g. busybox and busybox subpackages (busybox-mdev).
>>
>> Regards
>> Wolfgang Hauser
>>
>
> Thank all for the suggestions!
> I created a wiki page to summarize the mail threads:
> https://wiki.yoctoproject.org/wiki/Run_postinst_during_rootfs_generation
>
> Thanks,
> -- Dexuan
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



-- 
Tom Parkin
www.thesecretdogproject.com
Morality, like art, means drawing a line someplace /Wilde/