From owner-freebsd-ports@FreeBSD.ORG Fri Sep 22 07:32:34 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org 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 1145D16A412 for ; Fri, 22 Sep 2006 07:32:34 +0000 (UTC) (envelope-from mail@sysfault.org) Received: from smtprelay06.ispgateway.de (smtprelay06.ispgateway.de [80.67.18.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 327F043D78 for ; Fri, 22 Sep 2006 07:32:32 +0000 (GMT) (envelope-from mail@sysfault.org) Received: (qmail 9485 invoked from network); 22 Sep 2006 07:32:31 -0000 Received: from unknown (HELO medusa.sysfault.org) (936934@[81.14.190.201]) (envelope-sender ) by smtprelay06.ispgateway.de (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 22 Sep 2006 07:32:31 -0000 Received: from localhost ([127.0.0.1] helo=medusa.sysfault.org) by medusa.sysfault.org with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GQf0W-0003K5-1D; Fri, 22 Sep 2006 08:59:32 +0200 Received: (from marcus@localhost) by medusa.sysfault.org (8.13.1/8.13.1/Submit) id k8M6xVsY012776; Fri, 22 Sep 2006 08:59:31 +0200 (CEST) (envelope-from marcus) Date: Fri, 22 Sep 2006 08:59:30 +0200 From: Marcus von Appen To: freebsd-ports@freebsd.org, amdmi3@mail.ru Message-ID: <20060922065930.GA12712@medusa.sysfault.org> Mail-Followup-To: freebsd-ports@freebsd.org, amdmi3@mail.ru MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1" Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) X-Spam-Score: -4.4 (----) Cc: Subject: devel/guichan update and dependant ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marcus von Appen List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Sep 2006 07:32:34 -0000 --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I wonder how I should deal with the devel/guichan port, which got a new version, 0.5.0, some time ago. As the guichan developers broke API compatibility to 0.4.0, the games/diameter and games/tmw ports would have been broken on update at that time. Now the games/tmw port received a new version, 0.0.21, which relies on guichan 0.5.0 while games/diameter still needs 0.4.0 (as far as I can see there is currently no ongoing effort of the diameter developers to bring it up to guichan 0.5.0). Shall I simply break games/diameter for the rest of the platforms it supports to allow devel/guichan and games/tmw to be updated or how should we deal with that issue? A repo copy of guichan, e.g. guichan04, does not sound like a good idea to me as the guichan developers announced that the API might still change in other releases thus continously breaking any dependant port and applications. This would mean to have a lot of guichan ports just to satisfy two port needs (currently). Personally I would break games/diameter and keep it as broken until a compatible version of it will be released (or remove it in a year or so if nothing happens). Regards Marcus --n8g4imXOkfNTN/H1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFE4nSo/JpszXavhwRAq6UAJ9nqMDGIyuQ60uY0XeGXfmazIrG8QCfQJ7y fphUXnJ4qek2KG/a9zvgPts= =f1tK -----END PGP SIGNATURE----- --n8g4imXOkfNTN/H1--