From owner-freebsd-ports@FreeBSD.ORG Sun Jan 31 20:09:28 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 B163F1065672 for ; Sun, 31 Jan 2010 20:09:28 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ew0-f211.google.com (mail-ew0-f211.google.com [209.85.219.211]) by mx1.freebsd.org (Postfix) with ESMTP id 487558FC14 for ; Sun, 31 Jan 2010 20:09:27 +0000 (UTC) Received: by ewy3 with SMTP id 3so143946ewy.33 for ; Sun, 31 Jan 2010 12:09:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=+oyQXE6JRYg0Js7KxNrFGGMsXZhIz7aJLSYnjEq4brU=; b=dWoBE4g1JybiGn5uqen+cqOKzLxD6Z6eU5Ob0KOQ47tUXzdpzxdjc6q+gMpIUQTZkc Y0oPK3T5AO6J45EY8GFG+6ErzytwlVRYM7zlImhi+0F4eoqHdaqRU5s1PW63gEuoBDXq grLSVDcf1FZzsZln+QUdgxKAaHX8HObzNbdxM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=eiN232W0a+N2+Qqm5EJYgU3ibvYejJLbOcGzEJhmqEeXVj6+CkJXdFmWFsdHjze5Kf QPfIhF9+pEGWm19AYuopgO70nbK5KsjptbvvGG6CY80l+nBHhCBnRVtqpz018qmVNOky AnkoRvFNtZ6GMS0ubCrBacNcFEuSRWMYyV5AQ= MIME-Version: 1.0 Received: by 10.216.162.142 with SMTP id y14mr2069276wek.192.1264968566779; Sun, 31 Jan 2010 12:09:26 -0800 (PST) Date: Sun, 31 Jan 2010 15:09:26 -0500 Message-ID: From: "b. f." To: cpghost Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-ports@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: Sun, 31 Jan 2010 20:09:28 -0000 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. >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?