unmerge: use vardbapi._dblink() to simplify

The dblink constructor is complex and best avoided.

diff --git a/pym/_emerge/unmerge.py b/pym/_emerge/unmerge.py
index a6a330cd338d4ef51282e38b35ee0a50f56ab086..68b61edc2d5a8038254755ba2f541c0a4336e311 100644 (file)
--- a/pym/_emerge/unmerge.py
+++ b/pym/_emerge/unmerge.py
@@ -7,7 +7,6 @@ import logging
 import sys
 import textwrap
 import portage
-import portage.dbapi.vartree
 from portage import os
 from portage.output import bold, colorize, darkgreen, green
 from portage._sets import SETPREFIX
@@ -321,9 +320,7 @@ def unmerge(root_config, myopts, unmerge_action,
                                        msg = ("Not unmerging package %s since there is no valid reason "
                                                "for Portage to unmerge itself.") % (pkg.cpv,)
                                        skip_pkg = True
-                               elif portage.dbapi.vartree.dblink(pkg.category, pkg.pf,
-                                       settings=settings, treetype="vartree", vartree=vartree,
-                                       scheduler=scheduler).isowner(portage._python_interpreter):
+                               elif vartree.dbapi._dblink(cpv).isowner(portage._python_interpreter):
                                        msg = ("Not unmerging package %s since there is no valid reason "
                                                "for Portage to unmerge currently used Python interpreter.") % (pkg.cpv,)
                                        skip_pkg = True