From owner-freebsd-ports@FreeBSD.ORG Fri Mar 28 07:23:25 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C899E1065670 for ; Fri, 28 Mar 2008 07:23:25 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by mx1.freebsd.org (Postfix) with ESMTP id 5632A8FC1C for ; Fri, 28 Mar 2008 07:23:25 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail09.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m2S7NLsO009046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Mar 2008 18:23:23 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.1) with ESMTP id m2S7NLkh020441; Fri, 28 Mar 2008 18:23:21 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m2S7NKvo020440; Fri, 28 Mar 2008 18:23:20 +1100 (EST) (envelope-from peter) Date: Fri, 28 Mar 2008 18:23:20 +1100 From: Peter Jeremy To: Michel Talon Message-ID: <20080328072320.GV1310@server.vk2pj.dyndns.org> References: <20080327093344.GA79721@lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EDJsL2R9iCFAt7IV" Content-Disposition: inline In-Reply-To: <20080327093344.GA79721@lpthe.jussieu.fr> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-ports@freebsd.org Subject: Re: ports system woes X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Mar 2008 07:23:25 -0000 --EDJsL2R9iCFAt7IV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 27, 2008 at 10:33:44AM +0100, Michel Talon wrote: >Garrett Cooper wrote: >> We came to the conclusion that BDB should be used, as no other DB =20 >> backend / API exists in the base system (currently), and porting =20 >> SQLLite (while nice) appeared to be non-trivial to port=20 > >Are you kidding? The patch files are totally trivial modifications, >to include stdlib.h. The bigger one is in Makefile.in to take into >account these ones. OTOH, SQLite is currently a rapidly moving target. And a couple of versions have including warnings about backward/forward compatability. Both these points count against integrating SQLite into the base system. Note that one of the reasons for removing perl from the base system was the difficulty of tracking vendor changes. >However it should not be bad to evaluate a solution based on BerkeleyDB, >another one on sqlite, and chose based on merit, not on aversions. This is reasonable. Of course, this is probably 50% more effort than just doing one - and no-one has come forward with a single solution yet. >particular an obvious fact is that there are constant troubles when the >DB version number changes or the ruby adapter changes. If you use the base BDB1 then it never changes, though portupgrade can become very upset when it upgrades its own dependencies. > One may expect >that no such problems will occur with a very stable and standardized >language like it is offered by sqlite. SQL is standardised but its implementation in SQLite is not yet stable. > It would be >useful to compare what the BdB in the base system has to offer >compared to sqlite BDB1 only offers get/put/delete. There is no locking or atomicity (these are only available in the ports version). --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --EDJsL2R9iCFAt7IV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iEYEARECAAYFAkfsnOgACgkQ/opHv/APuIfESQCfRMQW7FLecc/Xt1uogXzwoauH 9b0AoJ2p3bubpH55/ehBQGaXj7nol5S2 =oIlc -----END PGP SIGNATURE----- --EDJsL2R9iCFAt7IV--