The portageq command in dev-db/postgis should contain the category. portageq match / postgis should be, portageq match / dev-db/postgis Thanks, Tim
Please explain what you're trying to do and submit the output of portageq. Are you complaining that portageq should require the use of <cat>/<pkg> to do the match or that it doesn't show the complete information for the installed package? You should also add the output of emerge --info so that we know what portage version you're using.
Well, I don't use emerge. The dev-db/postgis ebuilds don't work with paludis because the category isn't included in the portageq command. Verified that it does work by creating a new, edited ebuild in my local overlay. See http://trac.pioto.org/paludis/ticket/606#comment:1 for more info. Sorry, I should have included more info in the first post. Kindest regards, Tim
According to ebuild(5) a base atom consists of $CATEGORY/$PACKAGE, so I'd say it is a valid bug. Maybe Portage should be stricter here.
This is a very rare situation, considering that 'qgrep' only found the following relevant references to 'portageq': for wxpy_pkg in $(portageq match "${ROOT}" '=dev-python/wxpython-2.6*'); do for wxpy_pkg in $(portageq match "${ROOT}" '=dev-python/wxpython-2.6*'); do tmp="$(portageq match / ${CATEGORY}/${PN})" tmp="$(portageq match / postgis | cut -d'.' -f2)" tmp="$(portageq match / postgis | cut -d'.' -f2)" tmp="$(portageq match / postgis | cut -d'.' -f2)" tmp="$(portageq match / postgis | cut -d'.' -f2)" stylesheet=$(portageq best_version / app-text/docbook-xsl-stylesheets) The three other ebuilds use category/package. Kindest regards, Tim
(In reply to comment #3) > According to ebuild(5) a base atom consists of $CATEGORY/$PACKAGE, so I'd say > it is a valid bug. Maybe Portage should be stricter here. Thanks, this is now fixed in svn: http://sources.gentoo.org/viewcvs.py/portage?rev=10835&view=rev
I've fixed the postgis ebuilds.
