Date: 11 Dec 2005 09:38:56 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Ian Moore <no-spam@swiftdsl.com.au> Cc: freebsd-questions@freebsd.org Subject: Re: Removing a port without upsetting dependencies Message-ID: <44slszd7gf.fsf@be-well.ilk.org> In-Reply-To: <200512110916.28583.no-spam@swiftdsl.com.au> References: <200512110916.28583.no-spam@swiftdsl.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Ian Moore <no-spam@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...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44slszd7gf.fsf>