SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just notifying everyone that the download source links for flash player plugin at Slackbuilds are broken since Adobe seems to just remove older versions (and never mind their crazy version numbering system).
The only thing needed for the x64 package is a renaming the /usr/lib folder within the package to /lib64 and then copying the package into your /usr directory and the plugin into the /usr/lib64/mozilla/plugins directory.
Is it me, or this new player really has the ability to turn full screen videos into powerpoint slide show? Lucky i've got a package for older version on my other computer
The only thing needed for the x64 package is a renaming the /usr/lib folder within the package to /lib64 and then copying the package into your /usr directory and the plugin into the /usr/lib64/mozilla/plugins directory.
It is not a good idea to copy system files directly into system directories like /lib64 etc.
You should at least use src2pkg to make an installable package out of it. Then you have a record of the installation and an easy way to remove/upgrade the files should you need to.
BTW I can't exactly remember now but I believe you need to add some symlinks that are not included with the standard build. Untarring the source, adding a doinst.sh and running makepkg is the neat way to do this.
Folks... my post was not meant as a "only" do it this way....
It was meant for someone new who got intrigued by Slackware....
he/she read about it.... no easy package manager "out of the box"
...they decided to try it and when they first logged in they realized... SOMETHING is different from the oldest existing Linux distro.... it just feels like a ROCK right when it boots.... so different... no 300 updates waiting because it was done "right".... and yet it feels as solid as a rock but as nimble as a flat rock being skipped accross a pond..... it just GLIDES...
..but... youtube.com says you are outdated..... so you Google it and here comes Slackbuilds... and "oh no!.... it's broken at the moment.....
As a newbie.... scared to post in the oldest distro forum... hmmmm..... "maybe i'll move on? (that might cross their mind)"... (I keep seeing a lot of new "lazyness?" from some in Linux?)
...ReaperX7 they might not know what to do after going to Adobe labs
...psionl0 ... EXCELLENT advise about straight copying but ......as a newbie "what are symlinks? .... there goes another hour of Google
Folks... it was meant as an informational post for the UN-initiated (at least with Slackbuilds.org). Sorry If I was not too clear on that (which I wasn't)
It is not a good idea to copy system files directly into system directories like /lib64 etc.
You should at least use src2pkg to make an installable package out of it. Then you have a record of the installation and an easy way to remove/upgrade the files should you need to.
BTW I can't exactly remember now but I believe you need to add some symlinks that are not included with the standard build. Untarring the source, adding a doinst.sh and running makepkg is the neat way to do this.
That isn't the best idea true, but if you check the directory structure of the package, it's standard Linux directory structure, except for the /usr/lib path is incorrect for 64-bit builds and needs to be renamed simply /usr/lib64
Using the src2pkg tool alone would create a package with an incorrect directory structure.
Using the src2pkg tool alone would create a package with an incorrect directory structure.
True, but you could use explodepkg on it, make the necessary changes and run makepkg again.
If there is no compiling involved, you don't need src2pkg. You can create a package by hand. in fact, I have made a BLOG detailing just that - making a package by hand (in this case to enable the nvidia drivers).
The slackbuild includes the necessary symlinks for the flash plugin to work with all of the browsers in Slackware.
rpm2tgz is ok if there is no further fixes required.
Installing directly from the "tar" is not recommended because it does not create a record of what you have done. As a result, if you had to remove it some time down the track, your job would be harder.
Installing directly from the "tar" is not recommended because it does not create a record of what you have done. As a result, if you had to remove it some time down the track, your job would be harder.
You would only need to run:
Code:
rm /usr/lib/mozilla/plugins/libflashplayer.so
or:
Code:
rm /usr/lib64/mozilla/plugins/libflashplayer.so
How hard is that?
And is all that extra stuff that comes with recent versions of flash really necessary?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.