What is the best way to add flash to Slackware14? (Morphed into how to add a repo to sbopkg?)
 

What is the best way to add flash to Slackware14? Use AlienBOB's slackbuild script here with sbopkg?

Sbopkg will do it just fine for you. You can also download a flash package from Eric's site.

http://slackware.com/~alien/slackbui...player-plugin/

Thanks, hitest.

Is there a recommended way to go about this (going the sbopkg route) i.e. should I somehow make a .repo in /etc/sbopkg/repos.d that points to http://www.slackware.com/~alien/slackbuilds/?


Edit:
I was reading some of Ponce's material here and here I found via duckduckgo, but I'm still not quite sure how to best do this. Apparently I could edit 40-sbo.repo and add a line something like the, but then it would get blown away, to my understanding, whenever a sbopkg -r was done.
Maybe I could temporarily, whenever desired, edit these to lines in /etc/sbopkg/sbopkg.conf to the below
and then use sbopkg -V SBo-Eric -r and sbopkg -V SBo-Eric -i desiredpackage? Or maybe a 70-EricHameleers.repo should be created?

Thanks for the help and insight.

You have to realize that sbopkg is only for use with slackbuilds.org repositories which only contain SlackBuild scripts.
My own repository has Slackware packages... the SlackBuild scripts are there as well, I have those in order to comply with GPL and other license requirements. But you can not use sbopkg to (re-)compile my packages.

Eric

Why to use a so complicated way to install Flash ?

I DL the tar.gz in "Source Downloads (64bit)" : http://slackbuilds.org/repository/13...player-plugin/

and used this for the installation : http://slackerboyabhi.wordpress.com/...ackware-13-37/

Probably the best way to put it is that sbopkg is only for slackbuilds.org repositories and repositories that follow that identical structure and even those aren't officially supported. But person X can create an SBo-compatible repo and person Y can add a line/file to their repos and use X's repo.

But it is extremely important to underscore that sbopkg is not intended to work with, and can't work with, Slackware itself or alien's repo or any other non-SBo-structured repo. It needs category/app/files hierarchies and info files with certain fields and so on.

Personally, while most slackers are allergic to most binaries, this is alien we're talking about, and I use a few of his binaries (thanks!). So you could go that route but, for flash, 'sbopkg -i flash-player-plugin' is simplest for me and probably would be for you if you're already using sbopkg.

Ok, now I feel really dumb. I was about to post how I could not install the flash player via sbopkg's default repos since a sbopkg -s flash yielded no results. But, to do due dilligent before posting such, I did a sbopkg -s flash-player-plugin, based on slakmagik's post, and to my surprise, I got results. ///
Looks like an asterisk is needful when searching in sbopkg i.e. sbopkg -s flash* sufficed to find what I desired. If I had known this, I wouldn't have started the thread.

Alien Bob, thanks for your insight concerning your repository. I can consider this thread not in vain from learning this. Maybe when you have a moment, for the sake of noobs such as myself, you could update your readme to clarify your slackbuilds are there for documentational, rather than practical, purposes.

paradise, particularly if you are working source anyway, you may wish consider implementing slackbuilds.org's slackbuilds via sbopkg and familizaring yourself with queuefiles as well. If I went the binary route, I'd just be using debian. (OK, not true. I'd be using packman in Arch. Or perhaps still sufficing with slapt-get in Slackware or Vector, but that likely represents my lack of knowledge regarding the "Slackware way" of resolving dependency needs.)

I come from a background of if I couldn't get something via slapt-get, I went without or ended up breaking things with a insufficiently compatible binaries. I tinkered with Arch a couple of years ago, and I came to really like Pacman, but I started with Slackware and Slackware and Vector just feel like home, so when I had a recent urge to leave behind a rock solid old Vector install, found Arch's installer is broken on my computer, and I came across posts about sbpokg on Distrowatch, I'm glad I've come back to Slackware. I like the option of tweaking a slackbuild for new source release rather than having to wait for a binary creator to make and submit a new binary.


Thanks again.

Oh, the SlackBuild scripts are very much meant for practical use. After all, they are how my packages get built.
What I meant to say was that my repository primarily offers packages while slackbuilds.org offers build scripts only. You can use my packages without hesitation, or if you are paranoid you can (re-)build them yourself using the provided sources.

Eric

Cool deal. Thanks, Eric. I'll just make sure to not treat your build scripts as slackbuilds.org scripts i.e. not attempt to use them with sbopkg. Thanks for the clarification. A big thanks for the repo i.e. binaries you offer and maintain.

I'll actually plan on giving your builds scripts a go, using the provided sources, just for the learning process.

Thanks again

Install Google Chrome (using the SlackBuild provided in extra). It includes the most recent (11.5), fastest² and bug-fixed³ version of Flash currently available for Linux.

Yes, FOSS browsers are out of luck. But what is the point of running a BLOB plugin within a FOSS browser anyway?

²) hardware-accelerated even on Intel GPUs
³) correct video colors on nVidia GPUs

To be candid, I stopped trusting Google several years ago. I guess the cat is out of the bag though since I used Gmail for years and still do for unimportant stuff accordingly. ^^ Chrome is not a bad recommendation for many, I'm sure, though. I've simply chosen to not go that route, at least not at this time. Thanks for your post just the same.