From owner-freebsd-ports@FreeBSD.ORG Wed Jun 25 15:12:39 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 66B8137B401 for ; Wed, 25 Jun 2003 15:12:39 -0700 (PDT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 484A843FBF for ; Wed, 25 Jun 2003 15:12:38 -0700 (PDT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 660C51FFFFE; Thu, 26 Jun 2003 00:12:36 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 3DDC91FFFFD; Thu, 26 Jun 2003 00:12:35 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 9E269153DB; Wed, 25 Jun 2003 22:10:08 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 93D81153CE; Wed, 25 Jun 2003 22:10:09 +0000 (UTC) Date: Wed, 25 Jun 2003 22:10:09 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Christian Weisgerber In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS snapshot-20020300 cc: freebsd-ports@freebsd.org Subject: Re: Ports that don't run on !i386 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: Wed, 25 Jun 2003 22:12:39 -0000 On Wed, 25 Jun 2003, Christian Weisgerber wrote: [ports for commiting no working on !i386 archs] > So what should I do? This is a well known problem I think. I am voting for committing, including a comment in commit message and perhaps also a note in the close on the PR to the user to check bento log in a few days and see what / if s.th. goes wrong. I personally try to do this once my updates get commited. For alpha I already have an account on Compaq/HP testdrive. Though this is no fun from dialup access w/o screen(1). Also some users had been willing to provide shell access for ports testing. Introducing a port-testing queue (submit tarball with THIS layout, we will queue, try to build and notfiy you) would be and ideal solution but wouldn't help I guess and only cost lot of resources. Perhaps a summary of open build errors can be mailed once every two weeks or every month to the maintainer (the fenner page -sorted by maintainer- should already have all needed information). This perhaps would help to make more maintainers looking at the logs. -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/