Hi everyone! Feel stupid asking this but as a Linux/newbie I throw myself before the court.. In anticipation of the next full release of MPlayer soon to hit I would like to understand how to remove my current v0.90rc2 of MPlayer without doing damage to my system. I understand and have successfully removed RPM packages from the system, however when compiling and installing from source as in this case I don't have a hook on the proper procedure in either upgrading when the time comes or properly removing the target files. Any tips would be very much appreciated! Kirb, VE6IV
Hi everyone! Feel stupid asking this but as a Linux/newbie I throw myself before the court.. In anticipation of the next full release of MPlayer soon to hit I would like to understand how to remove my current v0.90rc2 of MPlayer without doing damage to my system. I understand and have successfully removed RPM packages from the system, however when compiling and installing from source as in this case I don't have a hook on the proper procedure in either upgrading when the time comes or properly removing the target files.
If the creator of MPlayer follows standard procedure (I think he/she/they do), simply go to your source directory and type: "make uninstall". (Note that if you installed as root, you will need to uninstall as root as well). This will remove the installed files that were created with "make install". I have been doing source updates on certain software packages, and with MPlayer, I would guess that you wouldn't even need to uninstall the old version unless the docs specifically say to or you want to install your new version to a new location. You can usually re-use your old ./configure command, keeping the same value for --prefix (/usr/local/ by default), make, and make install and the old version of MPlayer should simply be written over by the new one. HTH. Josh
Any tips would be very much appreciated!
jvollmer@visi.com
Hi everyone! Feel stupid asking this but as a Linux/newbie I throw myself before the court.. In anticipation of the next full release of MPlayer soon to hit I would like to understand how to remove my current v0.90rc2 of MPlayer without doing damage to my system. I understand and have successfully removed RPM packages from the system, however when compiling and installing from source as in this case I don't have a hook on the proper procedure in either upgrading when the time comes or properly removing the target files. Any tips would be very much appreciated!
1) install the gtk-devel-1.2.10 package using YaST2 (you'll need it.) 2) Untar Mplayer source into /tmp 3) cd into Mplayer-0.90rc2 directory created in step 2 4) ./configure --enable-gui (to enable the GUI.) 5) make 6) make install 7) remove Mplayer-0.90rc2 directory created in step 2 -- JAY VOLLMER JVOLLMER@VISI.COM TEXT REFS DOUBLEPLUSUNGOOD SELFTHINK VERGING CRIMETHINK IGNORE FULLWISE
Thanks to all. I enabled DMA for my scsi-emulated dvd drive. I tried a lot more, but as i figured, the simple process is as follows : Assuming that hdc is dvd drive and is scsi emulated 1. Add (or modify) hdc=ide-cd to grub parameters. Grub allows this while booting, you don't need to edit grub.conf. 2. Now that dvd is an ide drive, yast allows you to enable DMA for it. 3. Restart. hdc is still ide-scsi now; and also dma-enabled, as hdparm said. I can watch a dvd with no performance problems now. And i also can use cdrdao as i used to.. Thanks again..
On Tuesday 14 January 2003 05:27, Kirby Nesbitt wrote:
Hi everyone! Feel stupid asking this but as a Linux/newbie I throw myself before the court.. In anticipation of the next full release of MPlayer soon to hit I would like to understand how to remove my current v0.90rc2 of MPlayer without doing damage to my system. I understand and have successfully removed RPM packages from the system,
Removing mplayer using should be easy, using rpm (as you already know). <grumpy> However, KDE (or rather SuSE) seems to resemble Windows more and more, and I do not mean that as a compliment. Observe: % rpm --test -e MPlayer error: removing these packages would break dependencies: MPlayer is needed by kdebase3-SuSE-8.1-56 % <more grumpy> What???? An application is needed for the system, and removing it wil break things? Dang, where have I heard that before? </more grumpy> </grumpy> I did remove the MPlayer package, and it did not break anything vital. However, much to my surprise, I saw MPlayer being installed (unasked) again when I installed some other package. Bottom line: just leave it installed and install your freshly compiled mplayer in /usr/local (which is the default, if I'm not mistaken). Check that /usr/local/bin comes before /usr/bin in your PATH variable. Good luck. Paul.
Op woensdag 15 januari 2003 22:32, schreef Paul Uiterlinden:
On Tuesday 14 January 2003 05:27, Kirby Nesbitt wrote:
Hi everyone! Feel stupid asking this but as a Linux/newbie I throw myself before the court.. In anticipation of the next full release of MPlayer soon to hit I would like to understand how to remove my current v0.90rc2 of MPlayer without doing damage to my system. I understand and have successfully removed RPM packages from the system,
Removing mplayer using should be easy, using rpm (as you already know).
<grumpy> However, KDE (or rather SuSE) seems to resemble Windows more and more, and I do not mean that as a compliment. Observe:
% rpm --test -e MPlayer error: removing these packages would break dependencies: MPlayer is needed by kdebase3-SuSE-8.1-56 %
<more grumpy> What???? An application is needed for the system, and removing it wil break things? Dang, where have I heard that before? </more grumpy> </grumpy>
I did remove the MPlayer package, and it did not break anything vital. However, much to my surprise, I saw MPlayer being installed (unasked) again when I installed some other package.
Yes, of course as it is required by kdebase3-SuSE... If you look in the *spec file of kdebase3-SuSE you'll see that it is a "manual" administrated dependency. I assume this has been done by SuSE, to get a default (predictable) system. The same will happen with k3b, keramik, etc. The full list is: Requires (from the spec file): kdebase3,kdebase3-nsplugin,susewm,susetour,release-notes,ghostscript-fonts-std, k3b,icons,keramik,yast2-theme-SuSELinux,susewm-kcmyast If you don't like that rebuild the rpm with an altered spec file :) (though kdebase3* are of needed requirements of course). -- Richard Bos Without a home the journey is endless
On Wednesday 15 January 2003 23:28, Richard Bos wrote:
I did remove the MPlayer package, and it did not break anything vital. However, much to my surprise, I saw MPlayer being installed (unasked) again when I installed some other package.
Yeah yeah, sure. But I do not like the fact that applications are needed for "the system". If the system needs e.g. libraries that are used by the application as well, they should have split it up into two packages. That's my opinion, for what it is worth. Paul.
participants (6)
-
Jay Vollmer -
Josh Trutwin -
Kirby Nesbitt -
oeren＠ykb.com -
Paul Uiterlinden -
Richard Bos