On 02/18/2013 02:12 PM, Doug Goldstein wrote: > On Mon, Feb 18, 2013 at 9:11 AM, Guido Günther <agx@xxxxxxxxxxx> wrote: >> Hi, >> >> On Sat, Feb 16, 2013 at 02:32:36PM -0500, Cole Robinson wrote: >> [..snip..] >>> merge virtinst: >>> - no big clean up, just get it all + unit tests working >>> - merge history or just add code? >> >> Is there any pressing reason for this? It's great to have this as a >> separate python module for user in other tools/scripts. >> Cheers, >> -- Guido >> > > I'm going to second Guido here. I use virt-install and virt-clone A > LOT. Until there's similar command line or easily scriptable (e.g. a > few number of lines in Python to get the same behavior) API then I > don't see myself switching anytime soon. > Sorry, I should have been more clear. virt-install and virt-clone are NOT GOING AWAY. They will live in the virt-manager repo and and there will be zero change in their behavior. virt-install is forever a stable API. The change is that the backing 'virtinst' code will not be a publicly accessible python module, it will be code private to virt-* tools. This should have zero visible impact for uses of virt-*. - Cole _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
