[Openembedded-architecture] Changes that switching from smart to dnf will cause

[Alexander Kanavin]

On 02/17/2017 09:24 PM, Mark Hatle wrote:
>>
>> The external deferral script is only called when cross-installing
>> packages on the build host ('if D is defined, then defer-to-first-boot'
>> kind of thing). Why would it be needed on target?
>
> We've needed to do this type of installation in the past when doing 'factory'
> type installs.. I.e. one machine runs a small target rootfs setup script
> (invoking smart using a remote package feed to point to a filesystem location.
> We enable the 'D' so that deferred things will startup on first boot of the
> devices...)
>
> Again, corner cases.  Not exactly standard behavior.

Right, I thought so :) If you enable the D, then you can also package a 
deferral script together with the rootfs setup script, and include it 
into the image of the first machine. The script is given a name of the 
package, and then it can either extract the postinst directly (not sure 
if this can be done in the middle of an rpm transaction), or append the 
package name to a file, and that file would later be iterated over by 
the setup script with postinst extracted one by one via calling rpm -q 
(this is how the deferral is done at cross-install).

Alex