From owner-freebsd-ports@FreeBSD.ORG Sun Apr 10 18:32:26 2005 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 BD45416A4CE for ; Sun, 10 Apr 2005 18:32:26 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00A5843D41 for ; Sun, 10 Apr 2005 18:32:26 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1A42E5130F; Sun, 10 Apr 2005 11:32:23 -0700 (PDT) Date: Sun, 10 Apr 2005 11:32:22 -0700 From: Kris Kennaway To: Tom Nakamura Message-ID: <20050410183222.GA68744@xor.obsecurity.org> References: <1113124895.4417.231517896@webmail.messagingengine.com> <20050410093620.GA54508@xor.obsecurity.org> <1113126899.21063.231518663@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline In-Reply-To: <1113126899.21063.231518663@webmail.messagingengine.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-ports@freebsd.org cc: Kris Kennaway Subject: Re: Breaking Fox-toolkit down into fox10, fox12, fox14, etc? 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: Sun, 10 Apr 2005 18:32:27 -0000 --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 10, 2005 at 02:54:59AM -0700, Tom Nakamura wrote: > On Sun, 10 Apr 2005 02:36:20 -0700, "Kris Kennaway" > said: > > On Sun, Apr 10, 2005 at 02:21:35AM -0700, Tom Nakamura wrote: > > > I was thinking it would be a good idea to break down the fox-toolkit > > > into 'fox10', 'fox12', 'fox14', and (recently) 'fox15', instead of the > > > current 'fox' port (which tracks 1.0.x) and 'fox-devel' port (which > > > tracks 1.4.x). I say this because=20 > > > 1) 'fox' is rather old, and 'fox-devel' is the development branch whi= ch > > > is extremely new; having fox12 strikes a good balance; > > > 2) the current version of 'ruby-fox' (fxruby.org) is geared for > > > fox-1.2.x (which guarantees compatibiltiy), but instead with only a > > > 'fox' and 'fox-devel', ruby-fox builds with fox-1.4.x, which may > > > introduce incompatibilities.=20 > > > any thoughts? > >=20 > > Only the versions that are acually useful should be in the ports > > collection. e.g. if no ports need fox 1.0, it shouldn't be kept. I'd > > be surprised if there was a need for 4 distinct versions. > >=20 > > Kris >=20 > You haven't check how many tk ports there are recently, have you :-)? Of course I'm well aware of that, but it's a different case: all of those versions are in use, though we'd like to be able to remove the old ones. > Anyways, its mostly because developement on fox is extremely rapid, and > fxruby (uses 1.2.x) and fxpy (uses 1.0.x i think) can't keep up, so they > are still necessary; though 1.5.x is unneccesary, i think it would be a > good idea to have at least a fox12 Kris --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCWXE2Wry0BWjoQKURAjsdAJ9NbkdOM/lu8YbwTN6DFBE4SwieaQCgvEdZ D0QKUNeFSU1dxZSmYMxp/98= =ZvIJ -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn--