During OS programming for the PHI, the need exists to permanently install RPM's.
Is there a systematic solution for determining and generating changes required to the uOS on a per RPM basis?
Seems like the process would involve an initial analysis of the RPM for contents.
Then the appropriate modifications to the PHI filelist need implemented.
Any thoughts on additional requirements?
One option that I've overlooked is to use an NFS share as the root for the PHI.