From owner-freebsd-ports@FreeBSD.ORG Mon Aug 26 17:27:42 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6BBDE6B8 for ; Mon, 26 Aug 2013 17:27:42 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.server1.bsdforen.de (bsdforen.de [82.193.243.81]) by mx1.freebsd.org (Postfix) with ESMTP id 2E88722DE for ; Mon, 26 Aug 2013 17:27:41 +0000 (UTC) Received: from mobileKamikaze.norad (HSI-KBW-134-3-231-194.hsi14.kabel-badenwuerttemberg.de [134.3.231.194]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.server1.bsdforen.de (Postfix) with ESMTPSA id A37D3861E7; Mon, 26 Aug 2013 19:27:38 +0200 (CEST) Message-ID: <521B900A.6090001@bsdforen.de> Date: Mon, 26 Aug 2013 19:27:38 +0200 From: Dominic Fandrey MIME-Version: 1.0 To: Florian Smeets Subject: Re: xpi-* broken since firefox-22 References: <521B450C.6030606@bsdforen.de> <521B8975.2000601@smeets.im> In-Reply-To: <521B8975.2000601@smeets.im> Content-Type: text/plain; charset=ascii Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2013 17:27:42 -0000 On 26/08/2013 18:59, Florian Smeets wrote: > On 26.08.13 14:07, Dominic Fandrey wrote: >> I don't know whether that's a general problem or just affects me, >> but since Firefox 22 the xpi-* ports don't work for me any more. >> > > This was broken for a brief period, it should be fixed though. You might > need to reinstall the xpis so that the correct links are created. Thanks, when it happened I installed everything locally and that probably masks that the ports xpis work again. >> Any plugin/addon may be added to the ports collection if one or more >> of the following conditions are met: >> - The plugin/addon builds/contains native code >> - The plugin/addon is a dependency of another port >> - The plugin/addon improves the integration with the base system, >> .e.g. it adds support for common environment variables like LANG, >> HTTP_PROXY or TZ > > That's the plan anyway. I'm working on it. Enigmail and lightning will > stay, perhaps the MOZILLA-xpi ports, but I'm leaning to removing those > too, as they can be installed from addons.mozilla.org just fine. I'm > just busy and haven't put this up for approval/discussion, yet. I'm maintainer of 2 xpi- ports. I'm willing to continue maintaining them if this is the verdict. But my vote is on getting rid of them. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?