From owner-freebsd-ports@FreeBSD.ORG Sat Jun 7 16:30:20 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF18D37B401 for ; Sat, 7 Jun 2003 16:30:20 -0700 (PDT) Received: from mail.inka.de (quechua.inka.de [193.197.184.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97AA343FDD for ; Sat, 7 Jun 2003 16:30:19 -0700 (PDT) (envelope-from mailnull@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with gbsmtp id 19On8c-0007N7-02; Sun, 08 Jun 2003 01:30:18 +0200 Received: from kemoauc.mips.inka.de (localhost [127.0.0.1]) by kemoauc.mips.inka.de (8.12.9/8.12.6) with ESMTP id h57MxLcP048163 for ; Sun, 8 Jun 2003 00:59:21 +0200 (CEST) (envelope-from mailnull@localhost.mips.inka.de) Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.12.9/8.12.9/Submit) id h57MxLCg048162 for freebsd-ports@freebsd.org; Sun, 8 Jun 2003 00:59:21 +0200 (CEST) From: naddy@mips.inka.de (Christian Weisgerber) Date: Sat, 7 Jun 2003 22:59:20 +0000 (UTC) Message-ID: References: <20030607211633.GA78779@freefall.freebsd.org> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-ports@freebsd.org Subject: Re: ghostscript commits (fix of back out request) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jun 2003 23:30:21 -0000 Alexander Kabaev wrote: > your recent commits to ghostscript port have broken them for > users which legitimately use GS_OPTIONS environment variable > to pass default options to the gs binary. script/configure > scripts in ports abuse this variable for something absolutely > unrelated, i.e. the list of drivers to compile with the port. The updates/changes are not mine but were submitted by Tsuguru KATO . I can only perform very minimal testing of gs's functionality. > Could you please either back your changes out or fix them? If there is sufficient demand, I can back them out, but I'm hesitant about where this is leading. The only one who appears to care about maintaining ghostscript is Tsuguru. I don't want this to turn into a permanent deadlock because of people just vetoing any change that might break something they're concerned about while denying the benefits of updates to everyone else. I strongly suggest people (1) talk to Tsuguru who is probably more familiar with the issues and (2) take an active interest in those ports themselves. Since there is no maintainer I'll hardly object if somebody else decides to back out the update--and direct all the blame towards themselves in the act. -- Christian "naddy" Weisgerber naddy@mips.inka.de