From owner-freebsd-libh Sun Oct 28 5:19:38 2001 Delivered-To: freebsd-libh@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 6A3CC37B401; Sun, 28 Oct 2001 05:19:27 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 30E0415E; Sun, 28 Oct 2001 13:19:05 +0000 (GMT) Date: Sun, 28 Oct 2001 13:19:05 +0000 From: Josef Karthauser To: Alexander Langer Cc: The Anarcat , "Simon L. Nielsen" , Eric Melville , binup@FreeBSD.org, libh@FreeBSD.org Subject: Re: current project steps Message-ID: <20011028131905.A3223@tao.org.uk> References: <20011020202153.A76835@FreeBSD.org> <20011026135930.03D1637B406@hub.freebsd.org> <20011026165952.D11804@shall.anarcat.dyndns.org> <20011026221254.A36515@tao.org.uk> <20011026172027.F11804@shall.anarcat.dyndns.org> <20011026223033.A44573@tao.org.uk> <20011027131726.A68253@shall.anarcat.dyndns.org> <20011027210157.D1534@tao.org.uk> <20011028100459.A40262@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="cNdxnHkX5QqsyA0e" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011028100459.A40262@fump.kawo2.rwth-aachen.de>; from alex@big.endian.de on Sun, Oct 28, 2001 at 10:04:59AM +0100 Sender: owner-freebsd-libh@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 28, 2001 at 10:04:59AM +0100, Alexander Langer wrote: > Thus spake Josef Karthauser (joe@tao.org.uk): >=20 > Hi! Hi :) =20 > > It sounds to me that libh has its fingers in too many pies. It's not a > > clean API; >=20 > What is your definition of a clean API? >=20 I'm probably getting confused by the name 'libh'. So what you're really talking about is several libraries, each with separate API's? In that case my fears are abated. If there are orthogonal in functionality... my fear was that libh was one big library that was on one hand was a graphic interface, on another hand was a sysinstall type tool, on another hand was a packaging system, etc. That's a lot to bite in one chunk. > Each library can be interfaced on its own. > - file access (including FTP/HTTP fetch, MD5 and ZIP interface) > - database stuff > - UI layer > - package library > - disk (interface to libdisk etc) I'm interested in the package library part. It may be that what you call 'package library' is equivalent to the existing /usr/ports stuff, or it maybe that it's close to what we've been calling libpkg. I'll read the libh docs and see. > there are some dependencies, though: e.g. the package library needs the > database lib, for obvious reasons. >=20 > Btw: The abstraction of the place to store the package db information > (you mentioned, e.g. Oracle instead of a local directory) should be > trivial, since everything is handled via calls to functions of > the database lib. Even more, you are using a Database object (C++), > so it's very easy to just write a SQL interfacing Database object. Did you see the earlier discussion on this subject? I'd be interested in your comments on my proposal? Joe --cNdxnHkX5QqsyA0e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjvcBcgACgkQXVIcjOaxUBZ9lgCcDqqm94A1aK/0ZVZMf7h1TZ6C 4S4AnR/nvGUDevVP+dHJeFbjDJr371Vi =bELy -----END PGP SIGNATURE----- --cNdxnHkX5QqsyA0e-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-libh" in the body of the message