all gripe about security ...
Mozilla or chrome Midori etc
builds so far from the fresh downloaded page...
Created attachment 331114 [details]
Not much changed from 1.14.3 except the ebuild is a little more configurable.
Created attachment 331116 [details, diff]
Looks like version 2.1.2 has been released.
Since the package in the tree is severely outdated, and nobody in the mozilla herd has any interest at all in attempting to bring it up to date nor continue to bump it with every new mozilla release, this package has been masked for removal from the tree in 30 days.
*** Bug 410293 has been marked as a duplicate of this bug. ***
*** Bug 404575 has been marked as a duplicate of this bug. ***
*** Bug 442664 has been marked as a duplicate of this bug. ***
2.1.2 ebuild then I suppose
just hopefully the item gets bumped at least from time to time.
Created attachment 357132 [details]
ebuild, patch, and manifest for mozplugger-2.1.3
For whoever still needs / wants this package, here is an updated ebuild (with patch and manifest) for mozplugger-2.1.3.
Yeah, mozplugger *IS* needed, at least to include evince in the browser. So please, instead of "killing" it, update the ebuilds. This is something that:
2/ do the job
3/ has no other alternative.
Do any of you want to proxy-maintain it? If so, I'll add your email addresses to metadata and will drop the removal. Mozilla herd doesn't have the manpower to take care of it but if the userbase is willing to step up then I won't remove it from the tree.
I have no idea what it represents as a work flow... Mark or maybe Patrick might be better candidate for this (I can test, though. 2.1.3 does work, but mozplugger doesn't do what it did, ie, open evince /in/ the browser, now I have a separate window. So, some work is needed for upgrade instructions. I also had to run mozplugger-update )
Proxy maintenance means that you would check for and test updated versions of the softare by version-bumping the ebuilds, check for and provide fixes for bugs when they're filed here (you'll get CC'd on them by bug-wranglers), ensure the ebuild and package meets all QA checks, and that the package continues to work as expected.
Note, for instance, that the proposed ebuild here has a -big- QA violation related to the executable stack. Also src_configure is malformed (econf fails silently if ./configure doesn't exist?? i highly doubt emake will succeed if econf wasn't run). Couple that with the fact that apparently it still doesn't do what you want it to (launch evince within the browser) and I'm wondering if the package really isn't good enough to remain in the tree even after being bumped.
I'm willing to maintain it as I use this package as a part of my job (so I'll get paid to maintain it :). However, I could use a primer on ebuilds as most of what I've done in the past is very simple stuff.
http://devmanual.gentoo.org , 'man 5 ebuild', and eclass-manpages pretty well cover everything you'd need to know. Also be sure to learn how to use 'repoman' to check for various errors and QA issues.
Also, if you could post what you needed to do after installation to get this package (2.1.3) actually working with browsers (firefox-17.0.8 , chromium-latest-stable) that would be great; for me, the plugin is entirely ignored in firefox (it's loaded, i can see a proper registration in about:plugins, but no mime types are successfully processed), and it is reported as 'cannot load' in chromium. --enable-debug didn't provide any useful info in the log, and after trying everything I could think of for 30 mins or so I just gave up.
*** Bug 484522 has been marked as a duplicate of this bug. ***
Created attachment 359144 [details]
mozplugger ebuild 2.1.3 with QA ok
This one corrects the QA and repoman is (almost) happy (some warning about m4, don't know what to do with it).
Still doesn't work here, though...
Created attachment 360808 [details]
Updated/tidied ebuild; this one seems to work well enough for me.
(In reply to Ian Stakenvicius from comment #15)
> Also, if you could post what you needed to do after installation to get this
> package (2.1.3) actually working with browsers (firefox-17.0.8 ,
> chromium-latest-stable) that would be great
I didn't have to do anything special with SeaMonkey or Opera, but I can't speak for other browsers.
Created attachment 360810 [details, diff]
Patch to bring the build system a bit more in line with Gentoo standards, derived from the previous Makefile.in patch and extended
Created attachment 360812 [details, diff]
Patch to hopefully fix this issue:
(In reply to Arnaud Launay from comment #12)
> mozplugger doesn't do what it did, ie, open evince /in/ the browser, now I
> have a separate window.
Pretty please with sugar on top revert the removal?
Can I just re-add it with myself as maintainer?
The current release (April 2014) works with firefox 36.
For now, it's in my dev overlay (layman -a xmw)
(In reply to Michael Weber from comment #22)
> Can I just re-add it with myself as maintainer?
> The current release (April 2014) works with firefox 36.
> For now, it's in my dev overlay (layman -a xmw)
I don't think mozilla@ has any problem with it being in the tree, we just can't maintain it ourselves.
As far as I am concerned, go ahead and re-add it to the tree with yourself as maintainer. I just have no interest in maintaining it anymore.
I, too, would enjoy this coming back into the tree. I've been using the 2.1.3 ebuild from here in a local overlay with no troubles.
+*mozplugger-2.1.6 (10 Mar 2015)
+ 10 Mar 2015; Michael Weber <email@example.com> +metadata.xml,
+ Re-add new version.
Confirmed working. Thanks!