How to remove erroneous deps from pkgng
Reko Turja
reko.turja at liukuma.net
Fri Jul 20 17:30:55 UTC 2012
-----Original Message-----
From: Bryan Drewery
On 7/20/2012 11:57 AM, Reko Turja wrote:
> I'm testing out the pkgng system and somehow a port managed to pull
> devel/pkg-config into one low level port polluting whole db. "pkg check"
> just wants to install the annoying thing. Is there any way to get rid of
> that erroneous dependency?
Which port is pulling it in?
sqlite3
> >
> > In production system, these kind of errors should be somehow
> > correctable, especially if pkgng is to be used with ports as well.
> If the port defines invalid dependencies, it's not pkgng's problem, it's
> the port.
True that, but there should be way of pruning cruft from the pkg tree
anyway. Even if the system is going more and more to linux way for majority
of users (one package fits all) there should be some kind of allowance for
those who want to build their own ports, but do not have access to major
build clusters ;) Ability to build and customise ports has been major reason
for using freebsd for me.
If you get force-fed all the dependencies the port does not really need
something like portupgrade -a will become major PITA.
Kimmo Paasiala wrote:
> The port devel/pkg-config is used in many ports, there's no harm in
> installing it.
I'm not running Gnome nor any gnome stuff except glib2. "pkg-config" might
be used somewhere, but it's completely unneeded in my systems and just extra
baggage for building and tracking dependencies.
-Reko
More information about the freebsd-ports
mailing list