[SVN-Commit] r1479 - in trunk/www: linux-firefox linux-seamonkey seamonkey-i18n
Author: jbeich
Date: Wed Feb 5 15:25:54 2014
New Revision: 1479
Log:
update
Modified:
trunk/www/linux-firefox/Makefile
trunk/www/linux-firefox/distinfo
trunk/www/linux-seamonkey/Makefile
trunk/www/linux-seamonkey/distinfo
trunk/www/seamonkey-i18n/distinfo
Modified: trunk/www/linux-firefox/Makefile
==
--- trunk/www/linux-firefox/MakefileWed Feb 5 09:55:30 2014(r1478)
+++ trunk/www/linux-firefox/MakefileWed Feb 5 15:25:54 2014(r1479)
@@ -2,7 +2,7 @@
# $FreeBSD: head/www/linux-firefox/Makefile 336446 2013-12-14 13:42:06Z flo $
PORTNAME= firefox
-DISTVERSION= 27.0
+DISTVERSION= 28.0b1
PORTEPOCH= 1
CATEGORIES=www ipv6
MASTER_SITES= MOZILLA/${PORTNAME}/releases/${DISTVERSION}/linux-i686/en-US
Modified: trunk/www/linux-firefox/distinfo
==
--- trunk/www/linux-firefox/distinfoWed Feb 5 09:55:30 2014(r1478)
+++ trunk/www/linux-firefox/distinfoWed Feb 5 15:25:54 2014(r1479)
@@ -1,5 +1,5 @@
-SHA256 (firefox-27.0.tar.bz2) =
07a1ce2ee28c8d6c67bd2192c806bdce529deb0c6acd8a199632d73889bc20af
-SIZE (firefox-27.0.tar.bz2) = 30616243
+SHA256 (firefox-28.0b1.tar.bz2) =
d5fb7f7a7862969195a2e776deda99a7e6508c46c691070c97d6b38ff44390fd
+SIZE (firefox-28.0b1.tar.bz2) = 31274665
SHA256 (glib2-2.22.2-2.fc12.i686.rpm) =
e3b459c245ec14e7248e9de4b506963a4773407f3e58835db5070d0ed02ecc99
SIZE (glib2-2.22.2-2.fc12.i686.rpm) = 1162908
SHA256 (gtk2-2.18.3-19.fc12.i686.rpm) =
aea9cf7ffe9c8dae0faa2bf3d2aa1b2117c55dce03da72dcce8c268279ec0a4b
Modified: trunk/www/linux-seamonkey/Makefile
==
--- trunk/www/linux-seamonkey/Makefile Wed Feb 5 09:55:30 2014(r1478)
+++ trunk/www/linux-seamonkey/Makefile Wed Feb 5 15:25:54 2014(r1479)
@@ -2,7 +2,7 @@
# $FreeBSD: head/www/linux-seamonkey/Makefile 336446 2013-12-14 13:42:06Z flo $
PORTNAME= seamonkey
-DISTVERSION= 2.24b1
+DISTVERSION= 2.24
CATEGORIES=www mail news editors irc ipv6
MASTER_SITES= MOZILLA/${PORTNAME}/releases/${DISTVERSION}/linux-i686/en-US
Modified: trunk/www/linux-seamonkey/distinfo
==
--- trunk/www/linux-seamonkey/distinfo Wed Feb 5 09:55:30 2014(r1478)
+++ trunk/www/linux-seamonkey/distinfo Wed Feb 5 15:25:54 2014(r1479)
@@ -1,2 +1,2 @@
-SHA256 (seamonkey-2.24b1.tar.bz2) =
15459f10ec7af85aacb817a1c54e4b60eda9a41f651915d1e0110affcd5902cd
-SIZE (seamonkey-2.24b1.tar.bz2) = 29805447
+SHA256 (seamonkey-2.24.tar.bz2) =
ed4ad37ff9c5d0d36f66bf25b272698e6d5bcf828cfac694d15467d4a4014ce5
+SIZE (seamonkey-2.24.tar.bz2) = 29803592
Modified: trunk/www/seamonkey-i18n/distinfo
==
--- trunk/www/seamonkey-i18n/distinfo Wed Feb 5 09:55:30 2014(r1478)
+++ trunk/www/seamonkey-i18n/distinfo Wed Feb 5 15:25:54 2014(r1479)
@@ -1,25 +1,47 @@
SHA256 (xpi/seamonkey-i18n-2.24/seamonkey-2.24.be.langpack.xpi) =
1d2c583dd8bc513127d6f605f129d7675865f0e32ac294313b803a9690e87acf
SIZE (xpi/seamonkey-i18n-2.24/seamonkey-2.24.be.langpack.xpi) = 814307
+SHA256 (xpi/seamonkey-i18n-2.24/seamonkey-2.24.ca.langpack.xpi) =
40bb6f6ac6e3e2739777eb9b219c88e232e2b20437ec15ff93344cabd6f61047
+SIZE (xpi/seamonkey-i18n-2.24/seamonkey-2.24.ca.langpack.xpi) = 811480
+SHA256 (xpi/seamonkey-i18n-2.24/seamonkey-2.24.cs.langpack.xpi) =
5605ff0b35abd28c7e84b87d2a30434803f74263e53b8b1350a9836fafea71f7
+SIZE (xpi/seamonkey-i18n-2.24/seamonkey-2.24.cs.langpack.xpi) = 809460
+SHA256 (xpi/seamonkey-i18n-2.24/seamonkey-2.24.de.langpack.xpi) =
842fdef4a36a9f5f9ba99e51e4bd99e0890eb279ec151f1a6527c90d123a1997
+SIZE (xpi/seamonkey-i18n-2.24/seamonkey-2.24.de.langpack.xpi) = 816146
+SHA256 (xpi/seamonkey-i18n-2.24/seamonkey-2.24.en-GB.langpack.xpi) =
8da55c64db56bdb9356c51d21a4a09a4530541a38e946543496c60bdc60ef1d3
+SIZE (xpi/seamonkey-i18n-2.24/seamonkey-2.24.en-GB.langpack.xpi) = 781088
SHA256 (xpi/seamonkey-i18n-2.24/seamonkey-2.24.en-US.langpack.xpi) =
3fae3e80f0b046ee88133c949705264e7b002ec00b2ada403c5d811a77ae87d1
SIZE (xpi/seamonkey-i18n-2.24/seamonkey-2.24.en-US.langpack.xpi) = 782073
SHA256 (xpi/seamonkey-i18n-2.24/seamonkey-2.24.es-AR.langpack.xpi) =
c96e94479dc6819a0a60341cc661801d72fabf9343344a8dbcf782eece9cbf61
SIZE (xpi/seamonkey-i18n-2.24/seamonkey-2.24.es-AR.langpack.xpi) = 838204
SHA256 (xpi/seamonkey-i18n-2.24/seamonkey-2.24.es-ES.langpack.xpi) =
9c8ef69f5f142c52edde2c26e383af76a2f71accc816babb7a1d08986e05c335
SIZE (xpi/seamonkey-i18n-2.24/seamonkey-2.24.es-ES.langpack.xpi) = 811306
+SHA256 (xpi/seamonkey-i18n-2.24/seamonkey-2.24.fi.langpack.xpi) =
209e64e3e4132d05beb124f3642e57cd5a341d73e417644725c2a8060cd56a90
+SIZE (xpi/seamonkey-i18n-2.24/seamonkey-2.24
Making WebRTC available for FreeBSD
https://plus.google.com/110946378055202199166/posts/8iTsSCatk4x The process has been started : http://forums.freebsd.org/viewtopic.php?f=39&t=44691 Dependencies needed- referenced in "howto" and webrtc dependencies: libbrlapi from brltty. Benefits: Native client and sever side of WebRTC applications for FreeBSD and possibly other BSDs. Eliminated dependency for Linuixlator based applications thus cutting down on hardware resource use. Eliminated need for other simulated and emulated programs to run Skype or other voice-and-video binaries. I.e. Wine, VirtualBox, qemu, et cetera, et al. Since it is known that Sony's PS4 uses FreeBSD as the basis for its OS, WebRTC could be implemented as a native application on the platform/console thus allowing users to communicater in real time while gaming. Why am I proposing this? 1. Adrian Chadd asked on Google+ and nowhere else. I decided to bring his proposal to the public and attempt an initial starting phase. 2. Users would not be limited to having only a few selected operating systems at their disposal. Developers could easily communicate with each other. 3. Real time sharing/viewing of conventions. This would give the community another window into the development of FreeBSD. 4. Companies such as IxSystems and Sony would be able to contact develoers while simultaneously working on a FreeBSD/FreeBSD_based system. 5. FreeBSD developers would be able to give feedback on the development of WebRTC sources. Being that I am limited on resources, is it possible that others could take over what was started? ___ freebsd-gecko@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: Making WebRTC available for FreeBSD
Hey guys, not sure what this refers to. The G+ post talks about porting the gtalk plugin to freeBSD. WebRTC is an effort in the opposite direction (no plugins needed). Afaik there is a Chromium build for freeBSD that should support WebRTC (unless it's disabled at build). Niklas On Wed, Feb 5, 2014 at 1:14 PM, Joe Nosay wrote: > https://plus.google.com/110946378055202199166/posts/8iTsSCatk4x > > The process has been started : > http://forums.freebsd.org/viewtopic.php?f=39&t=44691 > > Dependencies needed- referenced in "howto" and webrtc dependencies: > libbrlapi from brltty. > > > Benefits: Native client and sever side of WebRTC applications for FreeBSD > and possibly other BSDs. > Eliminated dependency for Linuixlator based applications thus cutting down > on hardware resource use. > Eliminated need for other simulated and emulated programs to run Skype or > other voice-and-video binaries. I.e. Wine, VirtualBox, qemu, et cetera, et > al. > > Since it is known that Sony's PS4 uses FreeBSD as the basis for its OS, > WebRTC could be implemented as a native application on the platform/console > thus allowing users to communicater in real time while gaming. > > > Why am I proposing this? > 1. Adrian Chadd asked on Google+ and nowhere else. I decided to bring his > proposal to the public and attempt an initial starting phase. > 2. Users would not be limited to having only a few selected operating > systems at their disposal. Developers could easily communicate with each > other. > 3. Real time sharing/viewing of conventions. This would give the community > another window into the development of FreeBSD. > 4. Companies such as IxSystems and Sony would be able to contact develoers > while simultaneously working on a FreeBSD/FreeBSD_based system. > 5. FreeBSD developers would be able to give feedback on the development of > WebRTC sources. > > > > Being that I am limited on resources, is it possible that others could > take over what was started? > > > > > ___ freebsd-gecko@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: Making WebRTC available for FreeBSD
On Wed, Feb 5, 2014 at 4:27 PM, Niklas Enbom wrote: > Hey guys, not sure what this refers to. The G+ post talks about porting > the gtalk plugin to freeBSD. WebRTC is an effort in the opposite direction > (no plugins needed). Afaik there is a Chromium build for freeBSD that > should support WebRTC (unless it's disabled at build). > > Niklas > > > On Wed, Feb 5, 2014 at 1:14 PM, Joe Nosay wrote: > >> https://plus.google.com/110946378055202199166/posts/8iTsSCatk4x >> >> The process has been started : >> http://forums.freebsd.org/viewtopic.php?f=39&t=44691 >> >> Dependencies needed- referenced in "howto" and webrtc dependencies: >> libbrlapi from brltty. >> >> >> Benefits: Native client and sever side of WebRTC applications for FreeBSD >> and possibly other BSDs. >> Eliminated dependency for Linuixlator based applications thus cutting >> down on hardware resource use. >> Eliminated need for other simulated and emulated programs to run Skype or >> other voice-and-video binaries. I.e. Wine, VirtualBox, qemu, et cetera, et >> al. >> >> Since it is known that Sony's PS4 uses FreeBSD as the basis for its OS, >> WebRTC could be implemented as a native application on the platform/console >> thus allowing users to communicater in real time while gaming. >> >> >> Why am I proposing this? >> 1. Adrian Chadd asked on Google+ and nowhere else. I decided to bring his >> proposal to the public and attempt an initial starting phase. >> 2. Users would not be limited to having only a few selected operating >> systems at their disposal. Developers could easily communicate with each >> other. >> 3. Real time sharing/viewing of conventions. This would give the >> community another window into the development of FreeBSD. >> 4. Companies such as IxSystems and Sony would be able to contact >> develoers while simultaneously working on a FreeBSD/FreeBSD_based system. >> 5. FreeBSD developers would be able to give feedback on the development >> of WebRTC sources. >> >> >> >> Being that I am limited on resources, is it possible that others could >> take over what was started? >> >> >> >> >> > How is it implemented at build time? ___ freebsd-gecko@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: Making WebRTC available for FreeBSD
https://code.google.com/p/chromium/codesearch#search/&q=enable_webrtc&sq=package:chromium&type=cs On Wed, Feb 5, 2014 at 1:33 PM, Joe Nosay wrote: > > > > On Wed, Feb 5, 2014 at 4:27 PM, Niklas Enbom wrote: > >> Hey guys, not sure what this refers to. The G+ post talks about porting >> the gtalk plugin to freeBSD. WebRTC is an effort in the opposite direction >> (no plugins needed). Afaik there is a Chromium build for freeBSD that >> should support WebRTC (unless it's disabled at build). >> >> Niklas >> >> >> On Wed, Feb 5, 2014 at 1:14 PM, Joe Nosay wrote: >> >>> https://plus.google.com/110946378055202199166/posts/8iTsSCatk4x >>> >>> The process has been started : >>> http://forums.freebsd.org/viewtopic.php?f=39&t=44691 >>> >>> Dependencies needed- referenced in "howto" and webrtc dependencies: >>> libbrlapi from brltty. >>> >>> >>> Benefits: Native client and sever side of WebRTC applications for >>> FreeBSD and possibly other BSDs. >>> Eliminated dependency for Linuixlator based applications thus cutting >>> down on hardware resource use. >>> Eliminated need for other simulated and emulated programs to run Skype >>> or other voice-and-video binaries. I.e. Wine, VirtualBox, qemu, et cetera, >>> et al. >>> >>> Since it is known that Sony's PS4 uses FreeBSD as the basis for its OS, >>> WebRTC could be implemented as a native application on the platform/console >>> thus allowing users to communicater in real time while gaming. >>> >>> >>> Why am I proposing this? >>> 1. Adrian Chadd asked on Google+ and nowhere else. I decided to bring >>> his proposal to the public and attempt an initial starting phase. >>> 2. Users would not be limited to having only a few selected operating >>> systems at their disposal. Developers could easily communicate with each >>> other. >>> 3. Real time sharing/viewing of conventions. This would give the >>> community another window into the development of FreeBSD. >>> 4. Companies such as IxSystems and Sony would be able to contact >>> develoers while simultaneously working on a FreeBSD/FreeBSD_based system. >>> 5. FreeBSD developers would be able to give feedback on the development >>> of WebRTC sources. >>> >>> >>> >>> Being that I am limited on resources, is it possible that others could >>> take over what was started? >>> >>> >>> >>> >>> >> > > How is it implemented at build time? > ___ freebsd-gecko@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: Making WebRTC available for FreeBSD
On Wed, Feb 5, 2014 at 10:27 PM, Niklas Enbom wrote: > Hey guys, not sure what this refers to. The G+ post talks about porting the > gtalk plugin to freeBSD. WebRTC is an effort in the opposite direction (no > plugins needed). Afaik there is a Chromium build for freeBSD that should > support WebRTC (unless it's disabled at build). > Niklas WebRTC on FreeBSD YES YES YES!!! =) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-gecko@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: Making WebRTC available for FreeBSD
On Wed, Feb 5, 2014 at 4:44 PM, Niklas Enbom wrote: > I still don't get what you mean. WebRTC is a part of browsers (Chrome, > Firefox) not the operating system. Are you looking for a browser that runs > on freeBSD and supports WebRTC - or something else? > > > On Wed, Feb 5, 2014 at 1:36 PM, Joe Nosay wrote: > >> >> >> >> On Wed, Feb 5, 2014 at 4:33 PM, Joe Nosay wrote: >> >>> >>> >>> >>> On Wed, Feb 5, 2014 at 4:27 PM, Niklas Enbom wrote: >>> Hey guys, not sure what this refers to. The G+ post talks about porting the gtalk plugin to freeBSD. WebRTC is an effort in the opposite direction (no plugins needed). Afaik there is a Chromium build for freeBSD that should support WebRTC (unless it's disabled at build). Niklas On Wed, Feb 5, 2014 at 1:14 PM, Joe Nosay wrote: > https://plus.google.com/110946378055202199166/posts/8iTsSCatk4x > > The process has been started : > http://forums.freebsd.org/viewtopic.php?f=39&t=44691 > > Dependencies needed- referenced in "howto" and webrtc dependencies: > libbrlapi from brltty. > > > Benefits: Native client and sever side of WebRTC applications for > FreeBSD and possibly other BSDs. > Eliminated dependency for Linuixlator based applications thus cutting > down on hardware resource use. > Eliminated need for other simulated and emulated programs to run Skype > or other voice-and-video binaries. I.e. Wine, VirtualBox, qemu, et cetera, > et al. > > Since it is known that Sony's PS4 uses FreeBSD as the basis for its > OS, WebRTC could be implemented as a native application on the > platform/console thus allowing users to communicater in real time while > gaming. > > > Why am I proposing this? > 1. Adrian Chadd asked on Google+ and nowhere else. I decided to bring > his proposal to the public and attempt an initial starting phase. > 2. Users would not be limited to having only a few selected operating > systems at their disposal. Developers could easily communicate with each > other. > 3. Real time sharing/viewing of conventions. This would give the > community another window into the development of FreeBSD. > 4. Companies such as IxSystems and Sony would be able to contact > develoers while simultaneously working on a FreeBSD/FreeBSD_based system. > 5. FreeBSD developers would be able to give feedback on the > development of WebRTC sources. > > > > Being that I am limited on resources, is it possible that others could > take over what was started? > > > > > >>> >>> How is it implemented at build time? >>> >> >> The option is not available with make config on FreeBSD nor is brltty >> available on FreeBSD. The gyp files do not include any FreeBSD specific >> references. >> > > WebRTC will only work if it can be built natively on a system despite the browser type. In trunk/build/ there are the following operating systems: android, ios, linux, mac, win. Also, the jingle protocol has not been ported to FreeBSD. Are there any developers who use FreeBSD? Anyway, I was hoping that maybe someone much better than me in/with programming and the FreeBSD community would see the benefits of bringing this to FreeBSD and take over my efforts. My initial arguments for such are in the first email of this thread. ___ freebsd-gecko@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: Bug info: bug 833117, FreeBSD Port www/firefox, glib20 2.36.3 and clang-devel 3.4.r182968
Robert_Burmeister wrote > https://bugzilla.mozilla.org/show_bug.cgi?id=833117 >> FireFox 22 fails to launch as described in the bug report after updating >> glib20 to version 2.36.3. > > I have been able to distill out more information on the error, which acts > like > Mozilla bug 833117. > > I have isolated that building www/firefox with OPTIMIZED_CFLAGS invoking > -O3 > causes bug 833117 to manifest, > while building www/firefox with -O2 in make.conf allows FireFox to work > normally. > > The root cause appears to be a compiler optimization issue. This issue appears to be resolved when building Firefox 27.0,1 on FreeBSD 10.0 i386 Stable. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Bug-info-bug-833117-FreeBSD-Port-www-firefox-glib20-2-36-3-and-clang-devel-3-4-r182968-tp5835607p5883415.html Sent from the freebsd-gecko mailing list archive at Nabble.com. ___ freebsd-gecko@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: Making WebRTC available for FreeBSD
On Wed, Feb 5, 2014 at 4:58 PM, Joe Nosay wrote: > > > > On Wed, Feb 5, 2014 at 4:44 PM, Niklas Enbom wrote: > >> I still don't get what you mean. WebRTC is a part of browsers (Chrome, >> Firefox) not the operating system. Are you looking for a browser that runs >> on freeBSD and supports WebRTC - or something else? >> >> >> On Wed, Feb 5, 2014 at 1:36 PM, Joe Nosay wrote: >> >>> >>> >>> >>> On Wed, Feb 5, 2014 at 4:33 PM, Joe Nosay wrote: >>> On Wed, Feb 5, 2014 at 4:27 PM, Niklas Enbom wrote: > Hey guys, not sure what this refers to. The G+ post talks about > porting the gtalk plugin to freeBSD. WebRTC is an effort in the opposite > direction (no plugins needed). Afaik there is a Chromium build for freeBSD > that should support WebRTC (unless it's disabled at build). > > Niklas > > > On Wed, Feb 5, 2014 at 1:14 PM, Joe Nosay wrote: > >> https://plus.google.com/110946378055202199166/posts/8iTsSCatk4x >> >> The process has been started : >> http://forums.freebsd.org/viewtopic.php?f=39&t=44691 >> >> Dependencies needed- referenced in "howto" and webrtc dependencies: >> libbrlapi from brltty. >> >> >> Benefits: Native client and sever side of WebRTC applications for >> FreeBSD and possibly other BSDs. >> Eliminated dependency for Linuixlator based applications thus cutting >> down on hardware resource use. >> Eliminated need for other simulated and emulated programs to run >> Skype or other voice-and-video binaries. I.e. Wine, VirtualBox, qemu, et >> cetera, et al. >> >> Since it is known that Sony's PS4 uses FreeBSD as the basis for its >> OS, WebRTC could be implemented as a native application on the >> platform/console thus allowing users to communicater in real time while >> gaming. >> >> >> Why am I proposing this? >> 1. Adrian Chadd asked on Google+ and nowhere else. I decided to bring >> his proposal to the public and attempt an initial starting phase. >> 2. Users would not be limited to having only a few selected operating >> systems at their disposal. Developers could easily communicate with each >> other. >> 3. Real time sharing/viewing of conventions. This would give the >> community another window into the development of FreeBSD. >> 4. Companies such as IxSystems and Sony would be able to contact >> develoers while simultaneously working on a FreeBSD/FreeBSD_based system. >> 5. FreeBSD developers would be able to give feedback on the >> development of WebRTC sources. >> >> >> >> Being that I am limited on resources, is it possible that others >> could take over what was started? >> >> >> >> >> > How is it implemented at build time? >>> >>> The option is not available with make config on FreeBSD nor is brltty >>> available on FreeBSD. The gyp files do not include any FreeBSD specific >>> references. >>> >> >> > > WebRTC will only work if it can be built natively on a system despite the > browser type. In trunk/build/ there are the following operating systems: > android, ios, linux, mac, win. > > Also, the jingle protocol has not been ported to FreeBSD. > Are there any developers who use FreeBSD? > > Anyway, I was hoping that maybe someone much better than me in/with > programming and the FreeBSD community would see the benefits of bringing > this to FreeBSD and take over my efforts. My initial arguments for such are > in the first email of this thread. > Any file that I need to edit will be on the forums at the post listed earlier. For brltty-4.4, the edited file of usb_bsd.h to replace brltty-4.4/Programs/usb_bsd.h has been uploaded. All changes are made public and the software license is adhered to by me. @Adrian Chadd: While I am working on this, you and others can tell me if any editing error occurs or if a value returns false. As sson as brltty-4.4 can build natively on FreeBSD, I will include a ports Makefile so that the users will be able to create their own package of brltty-4.4, thus completing all dependencies. After that, I will return to building and editing WebRTC for FreeBSD. ___ freebsd-gecko@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
