ubuntu-webapps-bugs team mailing list archive

[Sam Segers <sam.sgrs@xxxxxxxxx>]

Public bug reported:

Could it be possible for click apps to have the plugin bundled?

An environment variable should be nice. Or in the
./lib/<triplet>/PepperFlash directory of the click app.

Now it's hard coded to the location of the adobe plugin or the chrome
version.

It would be nice to be able to package it with the click as it then
could be used on systems that don't have it.

I also have this problem with chrome-beta installed. I had to symlink
/opt/google/chrome-beta to /opt/google/chrome to make it work.

The same problem is true with chrome-daily.

** Affects: oxide
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1585379

Title:
  pepper plugin path is hard coded in the source

Status in Oxide:
  New

Bug description:
  Could it be possible for click apps to have the plugin bundled?

  An environment variable should be nice. Or in the
  ./lib/<triplet>/PepperFlash directory of the click app.

  Now it's hard coded to the location of the adobe plugin or the chrome
  version.

  It would be nice to be able to package it with the click as it then
  could be used on systems that don't have it.

  I also have this problem with chrome-beta installed. I had to symlink
  /opt/google/chrome-beta to /opt/google/chrome to make it work.

  The same problem is true with chrome-daily.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1585379/+subscriptions