I posted a package development plan to debian-amd64 not long ago outlining my intentions for nspluginwrapper on Debian over the coming versions. 1.0.0-2 will have a drastically slimmed down npconfig tool.
1.0.0-3 will be the beginning of the split package, and one of the intended features is to use nspluginwrapper as a sandbox for plugins to live (and die) in, which should cover your request. I really think the slimmed down npconfig is needed for 1.0.0-2, and moreover 1.0.0-3 as it's very specific where it wants to install plugin wrapper stubs. Hopefully then I can liase with other plugin packagers to use it as a sandbox. What concerns me a little is that some people (notably thin client users) have reported issues running plugins across xdmcp sessions. I shall have to investigate this before suggesting more widespread usage. Furthermore, nspluginwrapper is in contrib right now. For packages in main to use this, I think it's "policy" to move such a dependancy (nspluginwrapper) into main before this can happen. Whether or not this will be easy, I don't yet know! Bart, I think this is possibly a good idea. Personally, I only have an i386 laptop so for testing package changes on the move (I have three amd64 environments at home for wrapper checks). Flash runs happily enough, but I want to ensure that the thin client issue is completely resolved first. rob. -- rob andrews :: pgp 0xd6c3e484 :: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
