Removing a port without upsetting dependencies
Lowell Gilbert
freebsd-questions-local at be-well.ilk.org
Sun Dec 11 06:39:05 PST 2005
Ian Moore <no-spam at swiftdsl.com.au> writes:
> Hi,
> I have mplayer installed and at one stage I installed the mplayer-skins port
> as well. Then I got sick of dealing with the skins port being broken a lot
> because the source files are often unfetchable, so I removed the port (I
> can't remember what method I used to do that now).
>
> Ever since, when I do a portupgrade & mplayer or various ports that it is a
> dependency of get updated, my ports database gets upset because those ports
> are marked as having mplayer-skins as a stale dependency.
>
> For example, today I have:
> Stale dependency: mplayerplug-in-3.17 --> mplayer-skins-1.1.2_1 -- manually
> run 'pkgdb -F' to fix, or specify -O to force.
>
> I generally either delete the dependency or link it to mplayer-gtk-esound, but
> the dependency comes back next time mplayerplug-in gets updated.
>
> I assume I've just used the wrong method for deleting the mplayer-skins port &
> I need to re-install & delete it the correct way. If I'm right, how should I
> do that?
>
> If not, is there a way I can permanently remove the mplayer-skins port and not
> have it appear as a dependency of other ports?
Modify those "other ports," I guess.
That's kind of what dependency means; they "depend" on the dependencies...
More information about the freebsd-questions
mailing list