On Sun, Mar 30, 2014 at 03:15:21PM +0200, Rune Morling wrote: > After all, any sane developer would probably rather play around with > the adoption process on a non-production system such as a separate > box or even just a VM? Doubly so if we politely point out that we > explicitly point out that adoption is a currently a unidirectional > process and that we do not support the 'un-adoption' of a previously > 'adopted' f20 system?
unadoption is trivial, something like: conary q --labels | grep f20.flnx.org@f:20-c | xargs conary erase --interactive Translated: list all packages on the system, look for only the packages from the common conary label that doesn't come from F20, and erase them. That will leave you with the RPM database intact and only the RPMs installed. And --interactive so that they can confirm that it won't wipe out their system due to a typo... _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
