Date: Sat, 1 Dec 2012 13:48:36 -0800 (PST) From: Jakub Lach <jakub_lach@mailplus.pl> To: freebsd-ports@freebsd.org Subject: Re: Opera vulnerability, marked forbidden instead of update? Message-ID: <1354398516576-5765785.post@n5.nabble.com> In-Reply-To: <20121124225507.GD12528@portland1.byshenk.net> References: <20121123092631.3b0aff2f0902e02098c273b4@alkumuna.eu> <50AF3B4B.9030704@freebsd.org> <20121123143735.90c91a7d81dc73c39764bcd8@alkumuna.eu> <20121124225507.GD12528@portland1.byshenk.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1354398516576-5765785.post>