Add comments explaining the installation process.075bf4ee3d
Port details
www/firefox-esr153.5.1,2
Web browser based on the browser portion of Mozilla
- Maintainer
- gecko@FreeBSD.org
- Packages
- firefox-esr 153.5.1,2
- Upstream
- up to date
- CPE
mozilla:firefox_esrfrom the port- WWW
- https://www.firefox.com/
- Links
- cgit · VuXML
Unaddressed (0) · The CVE record lists this version as affected, no VuXML entry names the CVE
VuXML only (0) · listed, port not fixed yet
pkg audit reports nothing for this version.Fixed (189)
CVE-2026-4684, CVE-2026-4685, CVE-2026-4686, CVE-2026-4687, CVE-2026-4689, CVE-2026-4690, CVE-2026-4691, CVE-2026-4692, CVE-2026-4693, CVE-2026-4694, CVE-2026-4696, CVE-2026-4698, CVE-2026-4699, CVE-2026-4706, CVE-2026-4707, CVE-2026-4709, CVE-2026-4721
CVE-2026-0877, CVE-2026-0879, CVE-2026-0880, CVE-2026-0882, CVE-2026-0886
CVE-2026-0878, CVE-2026-0883, CVE-2026-0884, CVE-2026-0885, CVE-2026-0887, CVE-2026-0890, CVE-2026-0891
CVE-2025-13012, CVE-2025-13013, CVE-2025-13014, CVE-2025-13015, CVE-2025-13016, CVE-2025-13017, CVE-2025-13018, CVE-2025-13019, CVE-2025-13020
CVE-2024-11692, CVE-2024-11696, CVE-2024-11697, CVE-2024-11699
CVE-2024-9392, CVE-2024-9396, CVE-2024-9400, CVE-2024-9401, CVE-2024-9402, CVE-2024-9403
CVE-2019-11734, CVE-2019-11735, CVE-2019-11736, CVE-2019-11737, CVE-2019-11738, CVE-2019-11740, CVE-2019-11741, CVE-2019-11742, CVE-2019-11743, CVE-2019-11744, CVE-2019-11746, CVE-2019-11747, CVE-2019-11748, CVE-2019-11749, CVE-2019-11750, CVE-2019-11751, CVE-2019-11752, CVE-2019-11753, CVE-2019-5849, CVE-2019-9812
CVE-2019-11709, CVE-2019-11710, CVE-2019-11711, CVE-2019-11712, CVE-2019-11713, CVE-2019-11714, CVE-2019-11715, CVE-2019-11716, CVE-2019-11717, CVE-2019-11718, CVE-2019-11719, CVE-2019-11720, CVE-2019-11721, CVE-2019-11723, CVE-2019-11724, CVE-2019-11725, CVE-2019-11727, CVE-2019-11728, CVE-2019-11729, CVE-2019-11730, CVE-2019-9811
CVE-2019-11691, CVE-2019-11692, CVE-2019-11693, CVE-2019-11694, CVE-2019-11695, CVE-2019-11696, CVE-2019-11697, CVE-2019-11698, CVE-2019-11699, CVE-2019-11700, CVE-2019-11701, CVE-2019-7317, CVE-2019-9800, CVE-2019-9814, CVE-2019-9815, CVE-2019-9816, CVE-2019-9817, CVE-2019-9818, CVE-2019-9819, CVE-2019-9820, CVE-2019-9821
CVE-2019-9788, CVE-2019-9789, CVE-2019-9790, CVE-2019-9791, CVE-2019-9792, CVE-2019-9793, CVE-2019-9794, CVE-2019-9795, CVE-2019-9796, CVE-2019-9797, CVE-2019-9798, CVE-2019-9799, CVE-2019-9801, CVE-2019-9802, CVE-2019-9803, CVE-2019-9804, CVE-2019-9805, CVE-2019-9806, CVE-2019-9807, CVE-2019-9808, CVE-2019-9809
CVE-2018-18500, CVE-2018-18501, CVE-2018-18502, CVE-2018-18503, CVE-2018-18504, CVE-2018-18505, CVE-2018-18506
CVE-2018-12405, CVE-2018-12406, CVE-2018-12407, CVE-2018-17466, CVE-2018-18492, CVE-2018-18493, CVE-2018-18494, CVE-2018-18495, CVE-2018-18496, CVE-2018-18497, CVE-2018-18498
CVE-2018-12388, CVE-2018-12390, CVE-2018-12391, CVE-2018-12392, CVE-2018-12393, CVE-2018-12395, CVE-2018-12396, CVE-2018-12397, CVE-2018-12398, CVE-2018-12399, CVE-2018-12400, CVE-2018-12401, CVE-2018-12402, CVE-2018-12403
CVE-2017-16541, CVE-2018-12375, CVE-2018-12376, CVE-2018-12377, CVE-2018-12378, CVE-2018-12379, CVE-2018-12381, CVE-2018-12382, CVE-2018-12383
CVE-2018-12358, CVE-2018-12359, CVE-2018-12360, CVE-2018-12361, CVE-2018-12362, CVE-2018-12363, CVE-2018-12364, CVE-2018-12365, CVE-2018-12366, CVE-2018-12367, CVE-2018-12368, CVE-2018-12369, CVE-2018-12370, CVE-2018-12371, CVE-2018-5156, CVE-2018-5186, CVE-2018-5187, CVE-2018-5188
no CVE referenced
CVE-2018-5150, CVE-2018-5151, CVE-2018-5152, CVE-2018-5153, CVE-2018-5154, CVE-2018-5155, CVE-2018-5157, CVE-2018-5158, CVE-2018-5159, CVE-2018-5160, CVE-2018-5163, CVE-2018-5164, CVE-2018-5165, CVE-2018-5166, CVE-2018-5167, CVE-2018-5168, CVE-2018-5169, CVE-2018-5172, CVE-2018-5173, CVE-2018-5174, CVE-2018-5175, CVE-2018-5176, CVE-2018-5177, CVE-2018-5178, CVE-2018-5180, CVE-2018-5181, CVE-2018-5182, CVE-2018-5183
CVE-2018-5125, CVE-2018-5126, CVE-2018-5127, CVE-2018-5128, CVE-2018-5129, CVE-2018-5130, CVE-2018-5131, CVE-2018-5132, CVE-2018-5133, CVE-2018-5134, CVE-2018-5135, CVE-2018-5136, CVE-2018-5137, CVE-2018-5138, CVE-2018-5140, CVE-2018-5141, CVE-2018-5142, CVE-2018-5143
CVE-2018-5089, CVE-2018-5090, CVE-2018-5091, CVE-2018-5092, CVE-2018-5093, CVE-2018-5094, CVE-2018-5095, CVE-2018-5097, CVE-2018-5098, CVE-2018-5099, CVE-2018-5100, CVE-2018-5101, CVE-2018-5102, CVE-2018-5103, CVE-2018-5104, CVE-2018-5105, CVE-2018-5106, CVE-2018-5107, CVE-2018-5108, CVE-2018-5109, CVE-2018-5110, CVE-2018-5111, CVE-2018-5112, CVE-2018-5113, CVE-2018-5114, CVE-2018-5115, CVE-2018-5116, CVE-2018-5117, CVE-2018-5118, CVE-2018-5119, CVE-2018-5121, CVE-2018-5122
CVE-2017-7826, CVE-2017-7827, CVE-2017-7828, CVE-2017-7830, CVE-2017-7831, CVE-2017-7832, CVE-2017-7833, CVE-2017-7834, CVE-2017-7835, CVE-2017-7836, CVE-2017-7837, CVE-2017-7838, CVE-2017-7839, CVE-2017-7840, CVE-2017-7842
CVE-2017-7793, CVE-2017-7805, CVE-2017-7810, CVE-2017-7811, CVE-2017-7812, CVE-2017-7813, CVE-2017-7814, CVE-2017-7815, CVE-2017-7816, CVE-2017-7817, CVE-2017-7818, CVE-2017-7819, CVE-2017-7820, CVE-2017-7821, CVE-2017-7822, CVE-2017-7823, CVE-2017-7824, CVE-2017-7825
CVE-2017-7753, CVE-2017-7779, CVE-2017-7780, CVE-2017-7781, CVE-2017-7782, CVE-2017-7783, CVE-2017-7784, CVE-2017-7785, CVE-2017-7786, CVE-2017-7787, CVE-2017-7788, CVE-2017-7789, CVE-2017-7790, CVE-2017-7791, CVE-2017-7792, CVE-2017-7794, CVE-2017-7796, CVE-2017-7797, CVE-2017-7798, CVE-2017-7799, CVE-2017-7800, CVE-2017-7801, CVE-2017-7802, CVE-2017-7803, CVE-2017-7804, CVE-2017-7806, CVE-2017-7807, CVE-2017-7808
CVE-2017-5470, CVE-2017-5471, CVE-2017-5472, CVE-2017-7749, CVE-2017-7750, CVE-2017-7751, CVE-2017-7752, CVE-2017-7754, CVE-2017-7755, CVE-2017-7756, CVE-2017-7757, CVE-2017-7758, CVE-2017-7759, CVE-2017-7760, CVE-2017-7761, CVE-2017-7762, CVE-2017-7763, CVE-2017-7764, CVE-2017-7765, CVE-2017-7766, CVE-2017-7767, CVE-2017-7768, CVE-2017-7778
CVE-2017-5429, CVE-2017-5430, CVE-2017-5432, CVE-2017-5433, CVE-2017-5434, CVE-2017-5435, CVE-2017-5436, CVE-2017-5437, CVE-2017-5438, CVE-2017-5439, CVE-2017-5440, CVE-2017-5441, CVE-2017-5442, CVE-2017-5443, CVE-2017-5444, CVE-2017-5445, CVE-2017-5446, CVE-2017-5447, CVE-2017-5448, CVE-2017-5449, CVE-2017-5450, CVE-2017-5451, CVE-2017-5452, CVE-2017-5453, CVE-2017-5454, CVE-2017-5455, CVE-2017-5456, CVE-2017-5458, CVE-2017-5459, CVE-2017-5460, CVE-2017-5461, CVE-2017-5462, CVE-2017-5463, CVE-2017-5464, CVE-2017-5465, CVE-2017-5466, CVE-2017-5467, CVE-2017-5468, CVE-2017-5469
CVE-2017-5398, CVE-2017-5399, CVE-2017-5400, CVE-2017-5401, CVE-2017-5402, CVE-2017-5403, CVE-2017-5404, CVE-2017-5405, CVE-2017-5406, CVE-2017-5407, CVE-2017-5408, CVE-2017-5409, CVE-2017-5410, CVE-2017-5411, CVE-2017-5412, CVE-2017-5413, CVE-2017-5414, CVE-2017-5415, CVE-2017-5416, CVE-2017-5417, CVE-2017-5418, CVE-2017-5419, CVE-2017-5420, CVE-2017-5421, CVE-2017-5422, CVE-2017-5425, CVE-2017-5426, CVE-2017-5427
CVE-2017-5373, CVE-2017-5374, CVE-2017-5375, CVE-2017-5376, CVE-2017-5377, CVE-2017-5378, CVE-2017-5379, CVE-2017-5380, CVE-2017-5381, CVE-2017-5382, CVE-2017-5383, CVE-2017-5384, CVE-2017-5385, CVE-2017-5386, CVE-2017-5387, CVE-2017-5388, CVE-2017-5389, CVE-2017-5390, CVE-2017-5391, CVE-2017-5392, CVE-2017-5393, CVE-2017-5394, CVE-2017-5395, CVE-2017-5396
CVE-2016-9080, CVE-2016-9893, CVE-2016-9894, CVE-2016-9895, CVE-2016-9896, CVE-2016-9897, CVE-2016-9898, CVE-2016-9899, CVE-2016-9900, CVE-2016-9901, CVE-2016-9902, CVE-2016-9903, CVE-2016-9904
CVE-2016-5289, CVE-2016-5290, CVE-2016-5291, CVE-2016-5292, CVE-2016-5293, CVE-2016-5294, CVE-2016-5295, CVE-2016-5296, CVE-2016-5297, CVE-2016-5298, CVE-2016-5299, CVE-2016-9061, CVE-2016-9062, CVE-2016-9063, CVE-2016-9064, CVE-2016-9065, CVE-2016-9066, CVE-2016-9067, CVE-2016-9068, CVE-2016-9070, CVE-2016-9071, CVE-2016-9072, CVE-2016-9073, CVE-2016-9074, CVE-2016-9075, CVE-2016-9076, CVE-2016-9077
CVE-2016-2827, CVE-2016-5256, CVE-2016-5257, CVE-2016-5270, CVE-2016-5271, CVE-2016-5272, CVE-2016-5273, CVE-2016-5274, CVE-2016-5275, CVE-2016-5276, CVE-2016-5277, CVE-2016-5278, CVE-2016-5279, CVE-2016-5280, CVE-2016-5281, CVE-2016-5282, CVE-2016-5283, CVE-2016-5284
CVE-2016-0718, CVE-2016-2830, CVE-2016-2835, CVE-2016-2836, CVE-2016-2837, CVE-2016-2838, CVE-2016-2839, CVE-2016-5250, CVE-2016-5251, CVE-2016-5252, CVE-2016-5253, CVE-2016-5254, CVE-2016-5255, CVE-2016-5258, CVE-2016-5259, CVE-2016-5260, CVE-2016-5261, CVE-2016-5262, CVE-2016-5263, CVE-2016-5264, CVE-2016-5265, CVE-2016-5266, CVE-2016-5267, CVE-2016-5268
CVE-2016-2815, CVE-2016-2818, CVE-2016-2819, CVE-2016-2821, CVE-2016-2822, CVE-2016-2825, CVE-2016-2828, CVE-2016-2829, CVE-2016-2831, CVE-2016-2832, CVE-2016-2833
CVE-2016-2804, CVE-2016-2805, CVE-2016-2806, CVE-2016-2807, CVE-2016-2808, CVE-2016-2811, CVE-2016-2812, CVE-2016-2814, CVE-2016-2816, CVE-2016-2817, CVE-2016-2820
CVE-2016-1952, CVE-2016-1953, CVE-2016-1954, CVE-2016-1955, CVE-2016-1956, CVE-2016-1957, CVE-2016-1958, CVE-2016-1959, CVE-2016-1960, CVE-2016-1961, CVE-2016-1962, CVE-2016-1963, CVE-2016-1964, CVE-2016-1965, CVE-2016-1966, CVE-2016-1967, CVE-2016-1970, CVE-2016-1971, CVE-2016-1972, CVE-2016-1973, CVE-2016-1974, CVE-2016-1975, CVE-2016-1976
CVE-2015-7208, CVE-2016-1930, CVE-2016-1931, CVE-2016-1933, CVE-2016-1935, CVE-2016-1937, CVE-2016-1939, CVE-2016-1942, CVE-2016-1943, CVE-2016-1944, CVE-2016-1945, CVE-2016-1946, CVE-2016-1947
CVE-2015-7201, CVE-2015-7202, CVE-2015-7203, CVE-2015-7204, CVE-2015-7205, CVE-2015-7207, CVE-2015-7208, CVE-2015-7210, CVE-2015-7211, CVE-2015-7212, CVE-2015-7213, CVE-2015-7214, CVE-2015-7215, CVE-2015-7216, CVE-2015-7217, CVE-2015-7218, CVE-2015-7219, CVE-2015-7220, CVE-2015-7221, CVE-2015-7222, CVE-2015-7223
CVE-2015-4513, CVE-2015-4514, CVE-2015-4515, CVE-2015-4518, CVE-2015-7181, CVE-2015-7182, CVE-2015-7183, CVE-2015-7185, CVE-2015-7186, CVE-2015-7187, CVE-2015-7188, CVE-2015-7189, CVE-2015-7190, CVE-2015-7191, CVE-2015-7192, CVE-2015-7193, CVE-2015-7194, CVE-2015-7195, CVE-2015-7196, CVE-2015-7197, CVE-2015-7198, CVE-2015-7199, CVE-2015-7200
CVE-2015-4476, CVE-2015-4500, CVE-2015-4501, CVE-2015-4502, CVE-2015-4503, CVE-2015-4504, CVE-2015-4505, CVE-2015-4506, CVE-2015-4507, CVE-2015-4508, CVE-2015-4509, CVE-2015-4510, CVE-2015-4512, CVE-2015-4516, CVE-2015-4517, CVE-2015-4519, CVE-2015-4520, CVE-2015-4521, CVE-2015-4522, CVE-2015-7174, CVE-2015-7175, CVE-2015-7176, CVE-2015-7177, CVE-2015-7178, CVE-2015-7179, CVE-2015-7180
CVE-2015-4473, CVE-2015-4474, CVE-2015-4475, CVE-2015-4477, CVE-2015-4478, CVE-2015-4479, CVE-2015-4480, CVE-2015-4481, CVE-2015-4482, CVE-2015-4483, CVE-2015-4484, CVE-2015-4487, CVE-2015-4488, CVE-2015-4489, CVE-2015-4490, CVE-2015-4491, CVE-2015-4492, CVE-2015-4493
CVE-2015-2721, CVE-2015-2722, CVE-2015-2724, CVE-2015-2725, CVE-2015-2726, CVE-2015-2727, CVE-2015-2728, CVE-2015-2729, CVE-2015-2730, CVE-2015-2731, CVE-2015-2733, CVE-2015-2734, CVE-2015-2735, CVE-2015-2736, CVE-2015-2737, CVE-2015-2738, CVE-2015-2739, CVE-2015-2740, CVE-2015-2741, CVE-2015-2742, CVE-2015-2743, CVE-2015-4000
CVE-2011-3079, CVE-2015-0797, CVE-2015-0833, CVE-2015-2708, CVE-2015-2709, CVE-2015-2710, CVE-2015-2711, CVE-2015-2712, CVE-2015-2713, CVE-2015-2714, CVE-2015-2715, CVE-2015-2716, CVE-2015-2717, CVE-2015-2718, CVE-2015-2720, CVE-2015-4496
CVE-2012-2808, CVE-2015-0800, CVE-2015-0801, CVE-2015-0802, CVE-2015-0803, CVE-2015-0804, CVE-2015-0805, CVE-2015-0806, CVE-2015-0807, CVE-2015-0808, CVE-2015-0810, CVE-2015-0811, CVE-2015-0812, CVE-2015-0813, CVE-2015-0814, CVE-2015-0815, CVE-2015-0816
CVE-2015-0819, CVE-2015-0820, CVE-2015-0821, CVE-2015-0822, CVE-2015-0823, CVE-2015-0824, CVE-2015-0825, CVE-2015-0826, CVE-2015-0827, CVE-2015-0828, CVE-2015-0829, CVE-2015-0830, CVE-2015-0831, CVE-2015-0832, CVE-2015-0833, CVE-2015-0834, CVE-2015-0835, CVE-2015-0836
CVE-2014-8634, CVE-2014-8635, CVE-2014-8636, CVE-2014-8637, CVE-2014-8638, CVE-2014-8639, CVE-2014-8640, CVE-2014-8641, CVE-2014-8642, CVE-2014-8643
CVE-2014-1569, CVE-2014-1587, CVE-2014-1588, CVE-2014-1589, CVE-2014-1590, CVE-2014-1591, CVE-2014-1592, CVE-2014-1593, CVE-2014-1594, CVE-2014-1595
CVE-2014-1574, CVE-2014-1575, CVE-2014-1576, CVE-2014-1577, CVE-2014-1580, CVE-2014-1581, CVE-2014-1582, CVE-2014-1583, CVE-2014-1584, CVE-2014-1585, CVE-2014-1586
CVE-2014-1544, CVE-2014-1547, CVE-2014-1548, CVE-2014-1549, CVE-2014-1550, CVE-2014-1551, CVE-2014-1552, CVE-2014-1555, CVE-2014-1556, CVE-2014-1557, CVE-2014-1558, CVE-2014-1559, CVE-2014-1560, CVE-2014-1561
CVE-2014-1533, CVE-2014-1534, CVE-2014-1536, CVE-2014-1537, CVE-2014-1540, CVE-2014-1541, CVE-2014-1542, CVE-2014-1543, CVE-2014-1545
CVE-2014-1492, CVE-2014-1518, CVE-2014-1519, CVE-2014-1520, CVE-2014-1522, CVE-2014-1523, CVE-2014-1524, CVE-2014-1525, CVE-2014-1526, CVE-2014-1527, CVE-2014-1528, CVE-2014-1529, CVE-2014-1530, CVE-2014-1531, CVE-2014-1532
CVE-2014-1493, CVE-2014-1494, CVE-2014-1496, CVE-2014-1497, CVE-2014-1498, CVE-2014-1499, CVE-2014-1500, CVE-2014-1501, CVE-2014-1502, CVE-2014-1504, CVE-2014-1505, CVE-2014-1506, CVE-2014-1507, CVE-2014-1508, CVE-2014-1509, CVE-2014-1510, CVE-2014-1511, CVE-2014-1512, CVE-2014-1513, CVE-2014-1514
Commits (926)
Don't install unnecessary MacOS/Windows-related material.0512440803
* Fix broken installation (grrr..this fake thing is more trouble than it's worth) * Fix up some path issues in the Makefile * Minor fix to plug-in installation * Restore Franz's fix for the LD_LIBRARY_PATH PREFIX problem * Bump PORTREVISION15e0c52fd1
Backuo the previous commit before anyone notices. I have a big patch coming that will fix this and some other things. No need to bump PORTREVISION twice.fb900956d3
Fix accidental change of %%PREFIX%% to %PREFIX%% in patch-build_unix_run-mozilla.sh (new PORTREVISION). Noticed by: Franz Klammer of webonaut.com Pointy hat to: moi86b505c335
Fix a bug where @PREFIX@ was being substituted with the fake package prefix paths.4fb396918c
* Import the JPI_LIST changes from www/mozilla so that multiple JPI versions will be tried. There is one addition, though. JPI_LIST is now overrideable. [1] * Remove the bit about Perl version from pkg-message. We support all versions of Perl now. Requested by: ale5b6aacf246
Add Firefox after a repo copy from mozilla-firebird. Firefox is the next release of the Firebird web browser with a new name to avoid conflicts with the Firebird database. This is version 0.8. http://www.mozilla.org/products/firefox/releases/ * Update to 0.8 and change name to firefox [1] * Make PLIST from a fake installation [1] * Restore original credit and portname in Makefile [1] * Optionally install headers and IDL files [2] * Use PERL instead of REINPLACE_CMD in a few places [1] * Use OPTIONS * Enable the Inspector extension * Fix another possible esound related problem * Enable basic optimizations if WITH_DEBUG is not specified PR: 62631 [2] Submitted by: trevor [1] [2]6593022e89
* Fix a bug where Firebird would lock up after typing any text. This had to do with esound being installed, but not being used (e.g. when not running under the GNOME Desktop). What happens now is sound support is disabled by default. If you wish to enable Type Ahead Find sound support, edit your prefs.js file, and add:
user_pref("accessibility.typeaheadfind.enablesound", true);
* Make portlint happy by not including anything after bsd.port.post.mk
* Clean up the pkg-message a bit to reflect reality with respect to Perl
Thanks to casaveli on BSDForums for finding it was esound causing the lock up
as well as testing the patch mentioned above.61164983e3Bump PORTREVISION on all ports that depend on gettext to aid with upgrading. (Part 1)73f7c91b5d
Port ia64 support from www/mozilla.fb325c73d6
Use the SORT macro defined in bsd.port.mk.fdad5368da
Port to amd64 (note: needs ld-elf.so.1 bugfix to actually work) I've taken a chance and split the sparc64 and alpha mega-diffs up because sparc64 patched the result of alpha's patches, and amd64 needed to do the same again - but it was sorted lexically before alpha/sparc64. I've grouped the xptcall patches together since they are standalone and split up and merged the other infrastructure jumbo-patches. I also attempted to sync up the nspr vs firebird diffs for sparc64 and alpha because they disagreed. HOWEVER... While this port 'depends' on the nspr port, it doesn't actually *use* it. It should probably be removed from the LIB_DEPENDS list. Note that the amd64 xptcall code came from SuSE via the mozilla bugzilla database.7059589bd6
Don't build these ports on amd64. Approved by: portmgr (implicit)4889bf65b1
Add a new patch-Double.cpp that fixes the recent core dumps during post-build on Sparc64. Submitted by: tmm (bless that man)cad4a555e6
* Update the extensions list with a modern mozconfig.in * Add rich text editing (aka midas) support8da2ffb9c0
Correct the packing list.0c4a4c6924
Update to 0.7 with patch-config_preprocess.pl updated by obraun. De-support GTK+ 1.2 (requested by marcus). Trim COMMENT.7feccd9870
Mark as IGNORE on -STABLE Alpha.7dddab53c3
Use ${PTHREAD_LIBS} instead of hardcoded -pthread and -lc_r in a few places. This should help the KSE and libthr people use these applications (plus it lets them build on -CURRENT).23dad2b555Add back the PKGNAMEPREFIX was the accidentally removed in my previous commit.c962223045
Change the MASTER_SITE back to the official Mozilla FTP servers. Note, people reinstalling this port will have to do a make distclean first, or simply ignore the MD5 checksum.718fe1846c
Restore the patch to stop mozilla from crashing on some russian sites.55fc6b08a7
Fix the PLIST link. PR: 55310 Submitted by: Morten Rodal <morten@rodal.no> Pointy hat to: mea4c693ac35
Fix the GTK+-1.2 plist. To do this, we create one plist for GTK1 and one for GTK2. This is easier to maintain using the cons-plist target. Reported by: kris via bento1b4dbed476
Update to 0.6.1. This is mainly a bug fix release according to the release notes at http://www.mozilla.org/projects/firebird/release-notes.html, but it went from being based on Mozilla 1.4b to 1.5a.
Note, the master site may be temporary. The source tarball at
${MASTER_SITE_MOZILLA} was missing some key bits that prevented compilation.84361df012Create a static plist file to fix the package building problem with the new install mk code. However, keep Alan's plist generating code around since it's cool, and it helps maintainers quickly generate a new plist. PR: 54795 54799f37483ee74
Try my hand at removing the Perl 5.6.1 dependency. This port now builds and seems to work just fine out-of-the-box on -STABLE with the built-in Perl 5.00503.f70740038e
Use ${PERL5} to properly locate perl.
Submitted by: perky337ddf44a0Add mozilla-firebird after a repo move from phoenix. Mozilla Firebird is the browser reborn from the ashes of the Phoenix. * Update to 0.6 [1] * Add optional GTK+-2 support [2] * Add [untested] Sparc64 support [3] * Add [untested] Alpha support [4] * Do not compile with -O2 by default. Instead specify -DWITH_OPTIMIZED_CFLAGS to get extra optimizations * Link the Java Plug-in again Submitted by: Stijn Hoop <stijn@win.tue.nl> [1] Christopher Nehren <apeiron@comcast.net> [2] (based on) tmm and kris [3] Bernd Walter <ticso@cicely.de> [4] Minor fixes by: obrauned564c5560
transfer to gnome@c54cf098a4
Remove USE_GNOMENG.b33eaf3276
Clear moonlight beckons. Requiem mors pacem pkg-comment, And be calm ports tree. E Nomini Patri, E Fili, E Spiritu Sancti.7e52725f2a
Remove the renaming of Xft headers and library from the Xft (Xft2) port. Remove installing of Xft1 from XFree86-4-libraries, and add dependencies to the Xft port by all the ports that use it along with whatever patches are necessary. Approved by: portmgr (kris), marcus38805e871a
remove ignore setting based on lfp fonts66ddabe840
add missing dependency0e9c05b83d
Patch by Greg Rumple & JMC to hopefully fix end-of-download crash. I'll submit this fix back to the Mozilla team, since it will affect Mozilla 1.3a as well. Approved by: kris before departure (one of these days this update will end)05c21b9963
Fix really messed up BROKEN= blocks that happened with 0.5. Approved by: kris (all port of moving to 0.5)32861cab29
Put back link to java now that fonts have been identified as cause of crashes or start failures. Reviewed by:j Approved by: kris (last phase of phoenix 0.5 update)3eaf8044e2
The problem wasn't the patch, it was third party font ports. The patch has been restored, extra knobs have added, and extensive diagnostics have been added. PLEASE upgrade to this version. Approved by: kris (part of phoenix upgrade)ce7094e451
Finally, a release Phoenix that works and does not crash all the time. Approved by: kris (a long time ago)fdfcd30ddc
Backed down to 0.4_10 because 0.5 was borked.763b461efc
Update Phoenix to 0.5, the last release named Phoenix. Fixes a lot a bugs, adds some features, there is at least one crasher I've hit so far but I don't know if it is anomoly or not yet. Approved by: kris052c9b9ee5
1. Add a link to support the java plugin. Thanks to Khairil Yusof <kaeru@pd.jaring.my> for this tip. 2. Build the plist automagically in a post-install target. Approved by: kris5526661e03
Updated PORTREVISION to 8. Added patch from mozilla-devel to fix -CURRENT problem with accessing network sites. Submitted by: Hajimu UMEMOTO <ume@mahoroba.org> Approved by: krisecc5f6b3f2
Update maintainer utility for making distfiles from cvs checkouts. No significance to users of this port, unless you are making your own distfiles.d582a2294c
* PORTREVISION ==> 7. * Allow building under -CURRENT. * Changes in LDFLAGS and CPPFLAGS passed to configure. * Removed stale javascript dirs (venkman) from plist. * Updated mkdistfile to remove more unneeded dirs. Used to make a new distfile from a cvs checkout. For maintainers only, really. * Disable bi-directional text in config. * Remove dupes from mozconfig.in. The problem with the martian file selection dialogs is gone. I am not sure of the cause, but apparently it had to do with either which version of the NSPR libs phoenix runs with or the link order of libraries. I don't care, as long as it doesn't do it, 'cause I do not read Martian. Should be running against its own set of NSPR libs now. (Note: you can't just use ldd to check this since the startup scripts play all kinds of fun games.) You are advised to remove $HOME/.phoenix before running the new version.c7685d56b9
Accidentally forgot a dependency on libiconv.0c860fb85c
1. PORTREVISION ==> 6. 2. Remove components (4) of javascript debugger from plist.56fd26fcea
1. Broken for system perl. Sorry but we don't know yet how to make it work. 2. Disable javascript debugger (like we're at a stage where we want to do that .... hahaha). 3. Remove dupes from files/mozconfig.in. 4. Whack the share and include dirs in a post-install target (I know it's slower that way, but I'm gonna let Trevor work out how to do it otherwise, since he so kindly volunteered.) 5. We Thanks to Adam Weinberger for his valuable info about perl versions, and his continuing research. Thanks to everybody else who's tested, even if y'all did report the same thing. 8-) Finally, thanks to Warren Zevon, whose song My ****'s ****ed Up certainly applies to the early stages of this port.c842552dbf