From owner-freebsd-ports Wed Apr 19 15: 7:22 2000 Delivered-To: freebsd-ports@freebsd.org Received: from viper.lovett.com (hub.lovett.com [216.60.121.161]) by hub.freebsd.org (Postfix) with ESMTP id 4C9BD37B5B0 for ; Wed, 19 Apr 2000 15:07:19 -0700 (PDT) (envelope-from ade@lovett.com) Received: from anaconda.lovett.com ([10.0.0.6]) by viper.lovett.com with esmtp (Exim 3.13 #1) id 12i2cs-0003SK-00; Wed, 19 Apr 2000 17:07:14 -0500 Received: (from ade@localhost) by anaconda.lovett.com (8.9.3/8.9.3) id RAA71041; Wed, 19 Apr 2000 17:07:14 -0500 (CDT) (envelope-from ade@lovett.com) Date: Wed, 19 Apr 2000 17:07:14 -0500 From: Ade Lovett To: Robert Huff Cc: ports@FreeBSD.org Subject: Re: problem installing TKhylafax Message-ID: <20000419170714.O65428@lovett.com> References: <38F88263.46D9076D@rcn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38F88263.46D9076D@rcn.com>; from roberthuff@rcn.com on Sat, Apr 15, 2000 at 10:53:23AM -0400 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Apr 15, 2000 at 10:53:23AM -0400, Robert Huff wrote: > Hello: > I just tried to install tkhylafax-3.0b2 and got: > > [snip breakage] > > So, if one can't install one of the required componenets, shouldn't > tkhylafax be marked as broken? Not really. It's just an artefact of the way the dependencies work. Not an ideal situation, but non-trivial to fix. Having said that, the hylafax port has been broken with security problems for long enough (4 months) with no-one complaining about it, that hylafax and tkhylafax should simply be culled from the tree. -aDe -- Ade Lovett, Austin, TX. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message