Latest version in portage is 188.8.131.52.
Latest version of noscript is 184.108.40.206.
Please bump! Thank you!
If someone from mozilla team would handle asap would be appreciated, is known to fix a few crashes.
Ditto on the version bump!!!!
I've got a question but don't want to sound stupid. Why can't we just use the version from Mozilla or the noscript webpage? I run other Mozilla add-ons without issue. Is there some advantage to using this package from portage vs. what's available from the authors? Thanks in advance.
To anyone reading this, I don't think we even need this package anymore. I uninstalled this package since it was so stale and tried the one directly from Mozilla. It works perfectly. So as far as I can tell one only needs to use the "official" download, install it, then they'll be good to go.
I hope this helps
(In reply to comment #4)
> To anyone reading this, I don't think we even need this package anymore. I
> uninstalled this package since it was so stale and tried the one directly from
> Mozilla. It works perfectly. So as far as I can tell one only needs to use the
> "official" download, install it, then they'll be good to go.
> I hope this helps
I am actually in process of removing the package, It will make it much easier to maintain by the user threw addon manager then threw the tree.
There is a new version. If it is not needed anymore it should be removed from portage. Else it should be up to date in portage.
The new version is 220.127.116.11
noscript is going to be removed from the tree. You should now use the extension manager instead of portage for mozilla's extension except for extension requiring compilation.
More information on bug 315999.
Resolving this bug as "Wont fix".