Re: Removing a port without upsetting dependencies
On Monday 12 December 2005 03:54, Kent Stewart wrote: > On Sunday 11 December 2005 06:10 pm, RW wrote: > > On Saturday 10 December 2005 22:46, Ian Moore wrote: > > > 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). > > > > A much better solution is to: > > > > cd /usr/ports/multimedia/mplayer-skins && make config > > > > then deselect everything, but the default skin. > > > > Since I did that I haven't had any problem with unfetchable skins. > > If you go into distfiles/mplayer and rm all of the files that are out of > date, you won't have any problem either. IIRC, the names haven't > changed but the MD5 and sizes have and it won't refetch them until you > remove them. The skins aren't broken. There is something slightly out > of whack with the Makefile. > > There may be an easier way but cd and rm * works just fine. I've deleted the skin distfiles on several occasions and it's never been anything more that a one-off fix to problems with mismatched checksums for me. All of the current files are datastamped 25-Mar-2005, so it's probably just the case that the mplayer maintainers have stopped messing with them. Occasional checksum problems can be down to the porter, but recurring problems are usually down to sloppy version control by the original maintainers. Also, if you look at http://www.mplayerhq.hu/MPlayer/Skin/ there is only one version of each skin which is probably why these things are sometimes unfetchable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Removing a port without upsetting dependencies
On Monday 12 December 2005 14:24, Kent Stewart wrote: > On Sunday 11 December 2005 06:10 pm, RW wrote: > > On Saturday 10 December 2005 22:46, Ian Moore wrote: > > > 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). > > > > A much better solution is to: > > > > cd /usr/ports/multimedia/mplayer-skins && make config > > > > then deselect everything, but the default skin. > > > > Since I did that I haven't had any problem with unfetchable skins. > > If you go into distfiles/mplayer and rm all of the files that are out of > date, you won't have any problem either. IIRC, the names haven't > changed but the MD5 and sizes have and it won't refetch them until you > remove them. The skins aren't broken. There is something slightly out > of whack with the Makefile. > > There may be an easier way but cd and rm * works just fine. > > Kent Thanks for the suggestions. I'm going with the "choose the default skin only" idea - that way I don't have to editi the make file each time the port is updated. Cheers, -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc pgpNPP5cGxxbJ.pgp Description: PGP signature
Re: Removing a port without upsetting dependencies
On Sunday 11 December 2005 06:10 pm, RW wrote: > On Saturday 10 December 2005 22:46, Ian Moore wrote: > > 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). > > A much better solution is to: > > cd /usr/ports/multimedia/mplayer-skins && make config > > then deselect everything, but the default skin. > > Since I did that I haven't had any problem with unfetchable skins. > If you go into distfiles/mplayer and rm all of the files that are out of date, you won't have any problem either. IIRC, the names haven't changed but the MD5 and sizes have and it won't refetch them until you remove them. The skins aren't broken. There is something slightly out of whack with the Makefile. There may be an easier way but cd and rm * works just fine. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Removing a port without upsetting dependencies
On Saturday 10 December 2005 22:46, Ian Moore wrote: > 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). A much better solution is to: cd /usr/ports/multimedia/mplayer-skins && make config then deselect everything, but the default skin. Since I did that I haven't had any problem with unfetchable skins. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Removing a port without upsetting dependencies
Ian Moore <[EMAIL PROTECTED]> 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... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Removing a port without upsetting dependencies
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? Cheers, -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc pgpbRysYmUBDh.pgp Description: PGP signature
