Bug 193652 - [patch] update www/xpi-noscript
Summary: [patch] update www/xpi-noscript
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-gecko (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-15 08:54 UTC by Matthieu Volat
Modified: 2016-11-24 21:48 UTC (History)
2 users (show)

See Also:
mva: maintainer-feedback? (gecko)

Attachments
Patch to 2.6.8.36, keep default MASTERSITES (1.00 KB, text/plain)
2014-09-15 08:54 UTC, Matthieu Volat 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthieu Volat 2014-09-15 08:54:45 UTC 
Created attachment 147339 [details]
Patch to 2.6.8.36, keep default MASTERSITES

Hi,

As I'm often getting noscript errors, I checked and the port version (2.6.6.1, november 2012 at least, according to moz ftp) seems a bit outdated (last is 2.6.8.41 according to https://addons.mozilla.org/en-US/firefox/addon/noscript/?src=search).

Here is the thing: relying on moz archives, I'm only able to bump it to 2.6.8.36 (first patch) as it it the last available version using port's Makefile.xpi infra (strangely, you don't see the latest version here : ftp://ftp.mozilla.org/pub/mozilla.org/addons/722/, but they are available on addons.mozilla.com...)

Switching MASTER_SITES to the upstream url would allow us to bump to 2.6.8.41, but would that be wanted?
Comment 1 Marcus von Appen freebsd_committer freebsd_triage 2014-09-17 17:03:26 UTC 
Over to maintainer.
Comment 2 Kurt Jaeger freebsd_committer freebsd_triage 2016-11-24 21:21:26 UTC 
This no longer downloads, as far as I can tell. Can we closed it as "overcome by events" ?
Comment 3 Matthieu Volat 2016-11-24 21:25:21 UTC 
Wow, indeeed. Port must have been updated in the meanwhile.
Comment 4 Kurt Jaeger freebsd_committer freebsd_triage 2016-11-24 21:32:17 UTC 
No, the port is not updated, but mozilla has changed the dist methods -- so if you find a new way to work with that, the current version is 2.9.5.1 ?
Comment 5 Matthieu Volat 2016-11-24 21:35:42 UTC 
To be fair, given the update frequency of this plugin, my conclusion was that sadly, using ports to manage this addon was not practical and it was better to rely on mozilla update channels.