Hi Dan, You don't need to merge anything. All changes can be done by one updates image. We are creating updates image with new Blivet changes all the time. You can do this manually from anaconda source (with your changes) by calling: ./scripts/makeupdates -t <ANACONDA_TAG> -k Then you will see ./updates/ folder in the anaconda git root. You can copy whole blivet to the path: ./updates/run/install/updates/blivet That way you can test both Anaconda and Blivet changes together. Another solution is to use this tool: https://github.com/rhinstaller/devel-tools/tree/master/anaconda_updates Anaconda updates should be able to automate some steps but it requires additional configuration. Jirka On Mon, 2019-06-10 at 13:54 +0200, Dan Horák wrote: > Hi, > > there is a request for not installing the PReP partition on PPC > system > that don't really require it in bug 1303219 [1]. I've spend some time > working on it and I think I have the solution, see [2] for details. > Because the testing requires a bare-metal Power machine I'm now > thinking > how to allow testing it with the community in the least intrusive > way. > Right now my plan is to have the anaconda PR merged and use an > updates.img for the corresponding blivet change. This way anaconda > itself should work as before and only when used with the updates.img > it > should change the behaviour. What do you think? > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1303219 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1303219#c5 > > > With regards, > > Dan > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/anaconda-devel-list _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
