From owner-freebsd-hackers@FreeBSD.ORG Sat May 12 21:33:53 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 00FBE16A402 for ; Sat, 12 May 2007 21:33:53 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id E15F013C465 for ; Sat, 12 May 2007 21:33:52 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C5B021A3C1A; Sat, 12 May 2007 14:34:39 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E1B7052FB7; Sat, 12 May 2007 17:33:51 -0400 (EDT) Date: Sat, 12 May 2007 17:33:51 -0400 From: Kris Kennaway To: Ivan Voras Message-ID: <20070512213351.GA28544@xor.obsecurity.org> References: <20070512004209.GA12218@lpthe.jussieu.fr> <17989.8202.624522.136573@bhuda.mired.org> <20070512090935.GA13929@lpthe.jussieu.fr> <20070512193302.GA24673@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: freebsd-hackers@freebsd.org Subject: Re: DPS Initial Ideas X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 May 2007 21:33:53 -0000 --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 12, 2007 at 11:25:58PM +0200, Ivan Voras wrote: > Kris Kennaway wrote: >=20 > > First figure out what specific problems need to be solved, then figure > > out how to solve them, not the other way around. So far I have seen > > little discussion of how SQLite is necessary and sufficient for fixing > > fundamental issues. The argument in favour of SQL seems to boil down > > to "It's SQL! You can do more complex queries...if you wanted to". >=20 > I've posted some general ideas (resulting from my experience using the > package / port system, not developing for it): >=20 > 1. speed and simplicity of querying (single query vs traversing a tree > of text files) > 2. formal data constraints (UNIQUE, CHECK) > 3. transaction safety (a consequence of which is the ability to run > concurrent installs / updates) > 4. easy interface for 3d party tools >=20 > I admit again that I didn't develop anything with the package / ports > subsystems, so there might be other, bigger problems not solvable by > sqlite, but I believe the features above could at least solve > performance problems. That is the "sufficient" part but not the "necessary part". 1) and 3) are solvable using existing tools. 2 and 4 not so much, but you haven't described what problems they solve. Homework for SQLite advocates: write a 1-page essay on the following topic. "Rewriting the package tools to use SQLite will solve problem(s) ____ that exist in the current system. Compare and contrast to other possible solutions including Berkeley DB." > (I also agree there's no point in changing the ports infrastructure > itself, just the package tracking database in base system). Well, I was talking about both. Kris --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGRjK/Wry0BWjoQKURAkaSAJ4y4ll1Kg1XCFoIfZQELOjTc1+lyQCgg+uF ZEHgEEd1ozP/8OATRqOsOWE= =Dy6V -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s--