From owner-freebsd-libh Wed Apr 24 11:31:38 2002 Delivered-To: freebsd-libh@freebsd.org Received: from mired.org (dsl-64-192-6-133.telocity.com [64.192.6.133]) by hub.freebsd.org (Postfix) with SMTP id 6A23837B423 for ; Wed, 24 Apr 2002 11:31:34 -0700 (PDT) Received: (qmail 58189 invoked by uid 100); 24 Apr 2002 18:31:30 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <15558.64002.460056.942779@guru.mired.org> Date: Wed, 24 Apr 2002 13:31:30 -0500 To: Antoine Beaupre Cc: freebsd-libh@FreeBSD.org Subject: Re: packaging base In-Reply-To: <342BD734-57AF-11D6-AE88-0050E4A0BB3F@anarcat.ath.cx> References: <15558.62884.852620.270991@guru.mired.org> <342BD734-57AF-11D6-AE88-0050E4A0BB3F@anarcat.ath.cx> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: Mike Meyer X-Delivery-Agent: TMDA/0.52 (Python 2.2 on FreeBSD/i386) 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 In <342BD734-57AF-11D6-AE88-0050E4A0BB3F@anarcat.ath.cx>, Antoine Beaup= re typed: > Le Mercredi 24 avril 2002, =E0 02:12 , Mike Meyer a =E9crit : > > In <0DFF2010-57A8-11D6-AE88-0050E4A0BB3F@anarcat.ath.cx>, Antoine=20= > > Beaupre typed: > > Yes, everything needs to be registered. No, installworld doesn't ha= ve > > to go away. I can see an installworld target that "knows" what > > packages are part of the base system, and only installs the ones th= at > > are already installed. That's actually cleaner than using make.conf= > > variables. Buildworld can use similar tactics. > That's a very interesting idea. > That's why developping pkgAPI is so important: there will be a=20 > transparent way of getting this kind of information. Yeah. The interesting part will be the distinction between updating the sources and updating the binary. That's why I hoped you had something real to propose. The current ports mechanism makes upgrading sources then building and installing them - well, let's say interesting. > > This is potentially something I can work on. > That's why I'm bugging you with this. ;) I just want you to avoid=20 > thinking that libh is some kind of silver bullet that would take care= of=20 > this. It's not taking care of this. I believe it should eventually. I hadn't though about pulling the packages stuff out in parallel, though. > > Libh isn't, as I what little I know of tcl is enough to keep me fro= m=20 > > wanting to learn more. > libh is more than just tcl. There's a solid C++ API behind all this. As if that were an improvement. I'd rather learn TCL than write C++. The people doing the work like it, so they are free to use what they want. That it excludes me is my problem, not theirs. =09=09=09=09http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more inform= ation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-libh" in the body of the message