http://www.opera.com/support/mastering/sysadmin/#system-defaults-file
On 27 February 2012 10:02, Ian Whyman <[email protected]> wrote: > Can we not set this in the ebuild somehow? This would allow us to push > out a fixed version automatically, I am generally very hesitant to put > anything extra in skel and (IMO) we should be looking to migrate our > fixes back out into the packages themselves. > > On 27 February 2012 00:37, Sławomir Nizio <[email protected]> wrote: >> TL;DR: plugins path in Opera set up by default for new user accounts soon >> >> >> Currently if you want to use plugins in Opera, you need to enable plugin >> path (/usr/lib/nsbrowser/plugins) manually, because this path (which isn't >> probably universal across big distributions) is not enabled in Opera by >> default. >> >> I've committed a change to skel that adds this path, so from the next >> version of Sabayon *for newly created user accounts only, because it uses >> skel* plugins should work out of the box. >> >> (By the way, almost all HTML5 YouTube videos work without any plugin. Good >> job Opera and YouTubers!) >> >> For those who don't like it, it's easy to disable (Opera → Settings → >> Preferences → Advanced tab → Config → Plug-in Options button; or >> opera:plugins). >> You can also disable plugins selectively. >> I believe it's what most people want, however. >> >> The change will take effect a bit before next version of Sabayon appears, >> maybe earlier. Unless it would have been reverted if a reason arises… >> >> -- somewhat technical part, eg. "Why?", feel free to skip -- >> >> I've added the new required path and two other that are set up by Opera on >> my >> system by default. >> That is because I wanted to keep upstream's default that >> /usr/lib/opera/plugins is listed first (otherwise it wouldn't be first). >> >> /usr/lib is a symlink to /usr/lib64 on amd64 Sabayon systems, so it has to >> work >> there too. >> >> Regards >> >> > > > > -- > Ian Whyman > v00d00.net -- Ian Whyman v00d00.net
