From owner-freebsd-ports Mon Oct 13 04:26:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA14881 for ports-outgoing; Mon, 13 Oct 1997 04:26:07 -0700 (PDT) (envelope-from owner-freebsd-ports) Received: from bubble.didi.com (ncr-us9-11.ix.netcom.com [204.31.236.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA14872 for ; Mon, 13 Oct 1997 04:25:59 -0700 (PDT) (envelope-from asami@bubble.didi.com) Received: (from asami@localhost) by bubble.didi.com (8.8.7/8.8.5) id EAA07882; Mon, 13 Oct 1997 04:25:44 -0700 (PDT) Date: Mon, 13 Oct 1997 04:25:44 -0700 (PDT) Message-Id: <199710131125.EAA07882@bubble.didi.com> To: grog@lemis.com, mike@smith.net.au, ports@FreeBSD.ORG In-reply-to: <199710131021.DAA07317@bubble.didi.com> (asami@cs.berkeley.edu) Subject: Re: Ghostscript 5 port is broken From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * That it extracts jpeg and png is a feature and is required to build * gs5 (don't ask me why, I don't want to know). If it actually * *installs* both those ports, there's something amyss with your * bsd.port.mk. What does the $Id$ line say? Sorry for the false fire-extinguisher (as opposed to "false alarm"). This port *was* broken very recently, and I was talking from memory and a week-old ports tree. I just committed a fix. Satoshi