Opera vulnerability, marked forbidden instead of update?

Jakub Lach jakub_lach at mailplus.pl
Sat Dec 1 21:48:43 UTC 2012

About updating opera port, it's matter of updating plist to make 
sure that opera cleans up after deinstall properly.

Opera have a habit of silently adding new files between versions, 
so it's must be checked.

Speaking from user perspective, you don't even need to bump 
version in Makefile, nobody stops you from downloading from 
opera.com directly and using their installer as well as their 
uninstaller (they provide both). It works, and should always
work, as long FreeBSD is supported platform.

Just when something is in ports, it must be integrated into 
infrastructure fully.

View this message in context: http://freebsd.1045724.n5.nabble.com/Opera-vulnerability-marked-forbidden-instead-of-update-tp5763426p5765785.html
Sent from the freebsd-ports mailing list archive at Nabble.com.

More information about the freebsd-ports mailing list