Gentoo Archives: gentoo-dev

From: David Leverton <u01drl3@×××××××.uk>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] eselect module for choosing between gnash and netscape-flash
Date: Wed, 25 Oct 2006 08:22:10
Message-Id: 453A14BB.9080203@abdn.ac.uk
1 Hi,
2
3 (Sorry if this is a dupe. I tried sending it before, but it seems to
4 have disappeared into /dev/null.)
5
6 I wrote an eselect module for choosing between the browser plugins from
7 net-www/gnash and net-www/netscape-flash, and I was wondering if it
8 could be included in Gentoo (probably not in its current state...).
9
10 I haven't updated any ebuilds to use it yet, because some details are
11 still open for discussion, in particular the location the plugins should
12 be installed to. If you want to test it in the meantime, create a
13 /usr/lib{,64,32}/nsbrowser/plugins/flash directory, and move the
14 existing Flash .so's from /usr/lib{,64,32}/nsbrowser/plugins to the new
15 directory. eselect will name the plugins after their filenames, minus
16 the .so - possibly not very user-friendly, but this could be fixed by
17 either using a separate display name, or by installing them with nicer
18 names.
19
20 Note that changing the active plugin while the browser's running may or
21 may not work reliably, it's best to restart it each time. Don't think
22 that's a bug in the module, I'm sure there are enough of those as it is. ;-)
23
24 Another issue is that it currently only works system-wide. It could be
25 nice to let each user override the global preference, but I don't know
26 of any reliable way to do that. At least SeaMonkey doesn't allow the
27 user's plugin directory to override the global one.
28
29 Other things: the multilib bits aren't tested much, since unless I've
30 missed something there's no way to build gnash in 32-bit mode on an
31 AMD64 system. On the other hand, it works for 64-bit browsers with the
32 help of net-www/nspluginwrapper. Speaking of which, it would be nice if
33 the two could be made to cooperate a bit better. nspluginwrapper works
34 by generating stubs for all the plugins it finds at merge-time, but it
35 would need to know about the special plugin location. There are two
36 ways I can think of to do this: either patch nspluginwrapper (yuck) or
37 make its ebuild juggle the plugins appropriately (slightly less yuck,
38 but wouldn't work if the administrator tries to generate the stibs
39 manually later on, which is needed if nspluginwrapper is installed
40 before Flash). Any preferences?
41
42 That's all I can think of for now. Any comments are appreciated.

Attachments

File name MIME type
Deleted:flash-nsplugin.eselect-0.1 text/x-moz-deleted
flash-nsplugin.eselect-0.1 text/plain

Replies