Date: Sat, 15 Jan 2011 18:13:20 +0100 From: Thierry Thomas <thierry@FreeBSD.org> To: Marcin Cieslak <saper@saper.info> Cc: gecko <gecko@FreeBSD.org>, Beat Gaetzi <beat@FreeBSD.org> Subject: Re: Ports depending on SeaMonkey 1.1 (www/seamonkey) Message-ID: <20110115171320.GB60954@graf.pompo.net> In-Reply-To: <alpine.BSF.2.00.1101141405570.63117@y.fncre.vasb> References: <4D305599.1050005@FreeBSD.org> <alpine.BSF.2.00.1101141405570.63117@y.fncre.vasb>
next in thread | previous in thread | raw e-mail | index | archive | help
--SUOF0GtieIMvvwua Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello all, Le ven 14 jan 11 =E0 15:12:35 +0100, Marcin Cieslak <saper@saper.info> =E9crivait=A0: > We have a www/bugmenot-firefox that might possibly work with=20 > seamonkey 2.0 as well (or just require a one-line patch to do so). > Seamonkey 2.x has a much higher degree of extension compatibility.=20 > thierry@ is maintainer on this one. >=20 > www/bugmenot is a newer version of www/bugmenot-firefox > patched a bit to support older Mozillas and Seamonkeys (1.x) as well. >=20 > What could be done we could end up with one port that=20 > includes seamonkey 1.x and seamonkey 2.x bits included. > Usually it does interfere in any way. >=20 > Thierry, what's your thought? Well, I'm interested by your patch, so that we could have only one bugmenot port in the tree. Best regards, --=20 Th. Thomas. --SUOF0GtieIMvvwua Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk0x1bAACgkQc95pjMcUBaLMNQCgi8BrVpR+RUEhGmj51Ndy3x2E olYAn2paJmoH6doBZeSCAw5deFQ2cvfr =+TOJ -----END PGP SIGNATURE----- --SUOF0GtieIMvvwua--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110115171320.GB60954>