From owner-freebsd-questions Mon Mar 4 13:26:26 2002 Delivered-To: freebsd-questions@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 9F81837B400 for ; Mon, 4 Mar 2002 13:26:23 -0800 (PST) Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Postfix) with ESMTP id 6D59B5D06; Mon, 4 Mar 2002 13:26:23 -0800 (PST) To: Kent Stewart Cc: Peter Ulrich Kruppa , freebsd-questions@FreeBSD.ORG Subject: Re: ImageMagick port: source file not available In-reply-to: Your message of "Mon, 04 Mar 2002 13:14:27 PST." <3C83E3B3.6050109@owt.com> Date: Mon, 04 Mar 2002 13:26:23 -0800 From: "Kevin Oberman" Message-Id: <20020304212623.6D59B5D06@ptavv.es.net> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I completely agree, but Cristy has always taken the line of "fix it NOW" for minor bits and pieces. He's always been open to tweaking operations at a user's request on the fly which really makes me nervous. (Although it really helped me whan I needed a minor extension to the labeling capability.) The real problem is that ImageMagick has so many divergent parts...IamgeMagick, PerlMagick, Magick++, JMagick, and probably one or tow that I've never really played with. I think he should either split it up with a common library or go to a stable/development scheme similar to most larger packages as well as FreeBSD (stable/current). But the package belongs to Cristy and he makes the final call on this stuff. I've been using it for at least 7 years and seldom had problems with it. It just makes it really, really hard to keep a port up-to-date, especially soon after a new release. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message