Now, I presume the browser has been 're-jigged' to look for it in the new location.but all I can tell you is that in Puppy, at least, WideVine is, for now, totally 'invisible' to the browser. In recent releases, libwidevine has been moved into its own sub-directory. Previously, libwidevinecdm.so just sat in the main directory, and I guess the browser was coded to look for it there. I have to apologise here for the current lack of WideVine, so.ATM, this means no NetFlix, Amazon Prime, Spotify, etc.
A HUGE sigh of relief finally, I'd achieved what I'd been toying with for the last couple of years.a totally portable, self-contained, Puppy package of the world's most popular browser. I made my selection, OK'ed it.and up it came. Still after a few seconds, there appeared the small, initial Chrome window, asking if you want to make it the default browser, and should it send data to Big Brother's servers, etc. It was pretty much a foregone conclusion, I suppose, given that all Chromium 'clones' share more or less the same main code-base TBH, it was almost an anti-climax when I fired it up from the terminal. So I assembled an identical package for the newest version of Chrome, with permissions & exec commands all the same. Thinking about it, I realised the issues were the same as the Chrome-portable I tried building yesterday. So, I zipped the package & uploaded earlier today. Fingers crossed, I fired it up from the terminal held my breath, and.it bloody well worked! Neat. The wrapper-script got the 'run-as-spot' prefix on the exec line.and the launch script (separate, rather than sym-linked - as suggested by Fred, to get round the sym-link 'issue' for those running Puppy from FAT32) also got the 'run-as-spot' prefix on the exec-line, too. So the Brave directory got 'spot' permissions. Previously, I'd been trying to create an entire 'spot' environment within the package.but then I thought, 'Hang about, Mike you're doing your usual trick.over-thinking things again.
Download google chrome portable portable#
Earlier today, I got a PM from Mikeslr, with the suggestion that since I seemed to be 'on a roll' with these portables, why not take a crack at one for Brave? Not one to turn down a challenge, I set to.īrave is like Chrome, in that it insists on running as a 'normal user' ('spot'-related stuff, in other words.) Anyway initially, I was getting the exact same issues I'd had with trying to make a portable Chrome work - see above. I'd been following the thread by RickGT351 about getting the 'Brave' browser running in Xenialpup64. Complaints in the terminal about not being able to get a 'SingletonLock', and errors when it came to creating, and populating, the profile directory, so I put it on the back burner. I had a play around with getting a portable Chrome to run yesterday.but it wasn't playing ball.
Download google chrome portable code#
After some false starts, I finally cobbled together a set-up that worked (thanks to a snippet of code proffered by Fred), and put together a couple of packages the night before last. It worked well so well, in fact, that I began experimenting with my favourite Chromium 'clone', Iron. Purely at random, I started playing around with Opera a week ago. I've had the idea for doing one at the back of my mind for a long time, but it's only recently that several wee snippets of code have steadily come together all at the same time.as a result of which there's been an explosion of Chromium portable 'clones' over the last few days. I only started messing about with these Chromium-based 'portables' around a week ago.
This will be the last one from me.I promise!