From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15197 invoked from network); 14 May 2002 22:28:28 -0000 Received: from unknown (HELO fencepost.gnu.org) (199.232.76.164) by sources.redhat.com with SMTP; 14 May 2002 22:28:28 -0000 Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 177kl4-0002T5-00; Tue, 14 May 2002 18:27:02 -0400 Received: from natint.juniper.net ([207.17.136.129] helo=merlot.juniper.net) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 177kiN-000219-00 for ; Tue, 14 May 2002 18:24:15 -0400 Received: from juniper.net (hatzis-bsd.juniper.net [172.17.12.59]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id g4EMOER44928 for ; Tue, 14 May 2002 15:24:14 -0700 (PDT) (envelope-from hatzis@juniper.net) Message-ID: <3CE18E8E.8090607@juniper.net> From: Mel Hatzis User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.8) Gecko/20020206 X-Accept-Language: en-us MIME-Version: 1.0 To: help-gnats@gnu.org Subject: 'send-pr --database' is broken in 4.0 beta Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: help-gnats-admin@gnu.org Errors-To: help-gnats-admin@gnu.org X-BeenThere: help-gnats@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: General discussion about GNU GNATS List-Archive: Date: Tue, 14 May 2002 15:28:00 -0000 X-SW-Source: 2002-q2/txt/msg00028.txt.bz2 The send-pr program has a couple of bugs in it associated with the '--database' option. 1. invoking send-pr --database=xx doesn't work (a space is required between the '--database' and the 'xx'. Given the usage line, this is very misleading. 2. the '--database' option in send-pr simply sets the GNATSDB environment variable to whatever value is specified. This is inconsistent with the use of the --database option in all the other gnats programs and furthermore, won't work at all...it ends up pointing to the 'default' database. Regarding #2, I've previously mailed a few messages to the group with the subject 'use of GNATSDB'....I'd really like to see this working and will gladly submit a patch if people are interested in my proposed solution - to use a GNATSID environment variable in addition to GNATSDB. GNATSID would be set to database names that are defined in the databases file (e.g. GNATSID=otherdb) and GNATSDB will continue to work as documented (e.g GNATSDB=host:port:name:user:passwd) Since the databases file can define a database as being remote, the GNATSID variable will make it unecessary to spell out the host/port...they're already defined in the databases file. Anyone have an opinion. -Mel _______________________________________________ Help-gnats mailing list Help-gnats@gnu.org http://mail.gnu.org/mailman/listinfo/help-gnats