Slackbuilds flash-plugin source links
 

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).

You can now download the 32bit here: http://download.macromedia.com/pub/l..._080811.tar.gz
and the 64bit here: http://download.macromedia.com/pub/l..._080811.tar.gz

Note: until Rworkman fixes the slackbuild you can just edit the flash-player-plugin.Slackbuild this way...

line 24: change to VERSION=11b2
line 56 change to: tar xvf $CWD/flashplayer11_b2_install_lin_${SRC_ARCH}_080811.tar.gz -C $PKG

After that proceed as usual with http://slackbuilds.org/howto/

Cheers!

An easier way is to go to:

http://labs.adobe.com and download the latest builds there.

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.

Installing Alien Bob's packages is another option.

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 :)

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 :cry:

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)

Cheers ;)
...

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.

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).

Why so much commotion?

The OP had the best advice...

Just download the tar file from adobe and change the slackbuild to reflect the new tar file version.

The link in slackbuild is broken because flash is up to 11.b2 and the link in slackbuilds points to 11.b1 which has been taken off line by adobe.


simple :D

Is a SlackBuild for flash-plugin really necessary?

I always installed either from the tar or from the rpm using rpm2tgz and both options work perfectly

I tend to only use SlackBuilds when the official version doesn't compile without lots of hacking

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.

You would only need to run:
or:
How hard is that?
And is all that extra stuff that comes with recent versions of flash really necessary?

If you can remember where you installed the libflashplayer.so file and all the links to it then that is fine.

I don't trust myself to remember those details 12 months down the track.

I've never had to create any links to libflashplayer.so. If you put it in one of those two places I mentioned, it's available to all browsers.

Or you can put it in ~/.mozilla/plugins and not have to touch the lib64 directory at all. (Will only be available to a single user then.)