From owner-freebsd-ports@FreeBSD.ORG Mon Feb 1 12:50:42 2010 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3F8F106566C; Mon, 1 Feb 2010 12:50:42 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.freebsd.org (Postfix) with ESMTP id 63AF48FC21; Mon, 1 Feb 2010 12:50:42 +0000 (UTC) Received: from epia-2.farid-hajji.net (epia-2 [192.168.254.11]) by fw.farid-hajji.net (Postfix) with ESMTP id 73FB737A3C; Mon, 1 Feb 2010 13:50:38 +0100 (CET) Date: Mon, 1 Feb 2010 13:50:37 +0100 From: cpghost To: "b. f." Message-ID: <20100201125037.GA4011@epia-2.farid-hajji.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-questions@freebsd.org, freebsd-ports@FreeBSD.org, wes@freebsd.org Subject: Re: devel/poco-ssl BROKEN. Can I use TRYBROKEN? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2010 12:50:42 -0000 On Sun, Jan 31, 2010 at 03:09:26PM -0500, b. f. wrote: > > Hi, > > > > devel/poco-ssl has been marked > > BROKEN= bad plist > > for some time now. > > > > Since I urgently need it for devel work, and as I would prefer > > to use the port rather than compile POCO directly (which works > > too), I'm considering bypassing this BROKEN setting with: > > > > .if ${.CURDIR:M*/devel/poco-ssl} > > TRYBROKEN=yes > > .endif > > > > in /etc/make.conf. > > > > Is it okay, until devel/poco-ssl is fixed? > > You can do whatever you want on your own system. The reason given > for marking it BROKEN was a bad plist, and if that is the only thing > wrong with it, then you need only worry about it leaving unregistered > files behind after it is removed, or possibly conflicting with another > port. If that's alright with you, then you may as well use NO_IGNORE > or TRYBROKEN as a workaround. Okay, I've tried it on a test machine, and it seems to work alright (so far), at least with the few programs I've compiled. It looks like a bad plist only, and I think that I understand the ramifications of it, so I'll stick to this workaround until the port is fixed. > > Oh, btw, I'm still missing the poco-doc port which pulls in > > the POCO documentation. :-( > > Oh, well. If the maintainer won't do it, maybe you could take the > time to fix the plist and offer an option to install the docs? I'll have a look as soon as I grok the ports system and find out how to do that. ;-) Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/