| Summary: | Eselect module for flash-nsplugins | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Daniel Pielmeier <billie> |
| Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | enhancement | CC: | eselect, levertond |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Daniel Pielmeier
2008-06-16 17:47:10 UTC
I just found out that updating the timestamp of the plugin by touching it as root has the same effect like reinstalling the ebuild, because the browser selects the plugin with most recent timestamp. So another way of changing the default plugin would be updating the timestamp. Maybe the ebuilds doesn't have to be changed when using this method. I wrote something for this a couple of years ago, but there didn't seem to be much interest¹. After thinking a bit more about it, it's probably something that should be done on the browser side anyway, not a system-wide decision. At least SeaMonkey 2 CVS seems to have the ability to enable and disable individual plugins, and I assume Firefox 3 has too. I have no idea about other browsers. If anyone thinks my old code would be useful, though, they're quite welcome to pick it up. I might have a slightly newer version somewhere than what's in the archive (probably nothing too exciting, but maybe a little fix or two), so if you want I can dig that out. [1] http://thread.gmane.org/gmane.linux.gentoo.devel/43629 It is solved in firefox 3: https://bugzilla.mozilla.org/show_bug.cgi?id=339056 It seems to manage flash, java and media-player plugins. (In reply to comment #2) > If anyone thinks my old code would be useful, though, they're quite welcome > to pick it up. I might have a slightly newer version somewhere than what's > in the archive (probably nothing too exciting, but maybe a little fix or > two), so if you want I can dig that out. This it not a module that should go into eselect proper, but should be a separate new package. Therefore reassigning to maintainer-wanted. (In reply to comment #3) > It is solved in firefox 3: Should this bug be closed then? (In reply to comment #4) > (In reply to comment #3) > > It is solved in firefox 3: > > Should this bug be closed then? > If this was only an issue for firefox then I would say yes. I don't know how other web browsers do the plug in handling though. (In reply to comment #5) > If this was only an issue for firefox then I would say yes. I don't know how > other web browsers do the plug in handling though. Closing for now. |