<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 14 June 2014 09:22, Karanbir Singh <span dir="ltr"><<a href="mailto:mail-lists@karan.org" target="_blank">mail-lists@karan.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">On 06/14/2014 01:28 PM, Bob Lightfoot wrote:<br>
> Looks like a great lot of work, so thanks for the effort. As a<br>
> Fedora Testor I am puzzled somewhat though. Is there available<br>
> reading material and such as how I would go about using these rpm with<br>
> a qemu/kvm for testing without having the installer available yet?<br>
> Obviously I can test the install media when it exists just like I do<br>
> for Fedora, but using these trees of rpms is a new skill I am hoping<br>
> to add. Don't want to bog anyone down with explaining it in detail,<br>
> as I don't mind reading and teaching myself, just need pointed where<br>
> to look.<br>
<br>
</div>we also spend quite a bit of time looking at and working with the rpms<br>
themselves to make sure they built ok, carry the right metadata, and<br>
then work on the branding stuff - ideally that, and migration paths from<br>
6 to 7 are what we'd be expecting people to be consuming and testing here.<br>
<br></blockquote><div><br></div><div>Here is an idea from what I did for the CentOS-5 days. Install the Fedora-19 with a minimal set of packages. Try and update the OS from the CentOS tree and see if that works. </div><div>
<br></div><div>Look for packages that were in Fedora 19 minimal and not in the CentOS tree and see if they can be removed. If they can't be then record that as "cruft".</div><div> </div></div><div>Reboot and see if that works. If it does then use that mostly CentOS-6.9901 as your initial image to run from and begin testing more packages from there.<br>
</div><div><br></div>-- <br><div dir="ltr">Stephen J Smoogen.<br><br></div>
</div></div>