Hello,
I cannot tell ATM (I'm travelling), but I'll check when back @home.
Regards,
--
Thierry Thomas
___
freebsd-gecko@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gecko
To unsubscribe, send any mail to &quo
Le Sam 7 aoû 10 à 10:50:59 +0200, Beat Gaetzi
écrivait :
> Hi Thierry,
Hello,
> On 06.08.2010 22:06, Thierry Thomas wrote:
> > I cannot tell ATM (I'm travelling), but I'll check when back @home.
>
> It looks like pango support is enabled by default in SeaMonkey 2.
Hello all,
Le ven 14 jan 11 à 15:12:35 +0100, Marcin Cieslak
écrivait :
> We have a www/bugmenot-firefox that might possibly work with
> 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.
> thierry@ is mainta
Le ven 14 jan 11 à 14:54:33 +0100, Beat Gaetzi
écrivait :
> Hi, (maintainers BCC'ed)
Hello Beat,
> There are still a couple of ports which depends on obsolete SeaMonkey
> 1.1 (www/seamonkey). We will replace SeaMonkey 1.1 with 2.1 as soon as
> 2.1 is released. Therefore we need to cleanup the p
>Submitter-Id: current-users
>Originator:Thierry Thomas
>Organization: Kabbale Eros
>Confidential: no
>Synopsis: www/seamonkey-i18n: options sometimes ignored
>Severity: non-critical
>Priority: low
>Category: ports
>Class: sw-bug
Hello,
Trying to upgrade www/xpi-ublock_origin to the latest release (1.14.4),
I'm facing a problem: the common targets for xpi- ports, located in
www/xpi-adblock/Makefile.xpi, relies upon install.rdf and
chrome.manifest. These two files exist for the legacy addons, but no
more for the new WebExte
Le jeu. 15 mars 18 à 18:04:06 +0100, Mikhail T.
écrivait :
> > Although wonderful on amd64, the recent versions of Firefox have been
> > remarkably unstable on the two i386 systems I maintain.
> >
> > Fortunately, a crash in a tab does not bring down the entire program.
> > Unfortunately, some
