From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27853 invoked from network); 3 May 2004 04:47:31 +0000 Received: from smtp.gentoo.org (128.193.0.39) by eagle.gentoo.oregonstate.edu with DES-CBC3-SHA encrypted SMTP; 3 May 2004 04:47:31 +0000 Received: from lists.gentoo.org ([128.193.0.34] helo=eagle.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.24) id 1BKVMY-0007Kr-Rm for arch-gentoo-dev@lists.gentoo.org; Mon, 03 May 2004 04:47:30 +0000 Received: (qmail 20197 invoked by uid 50004); 3 May 2004 04:47:30 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 12311 invoked from network); 3 May 2004 04:47:30 +0000 From: John Nilsson To: Paul de Vrieze Cc: gentoo-dev@lists.gentoo.org In-Reply-To: <200405021156.04790.pauldv@gentoo.org> References: <1083296558.8842.127.camel@woot.uberdavis.com> <200405021156.04790.pauldv@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-oZY73FstZXZiUvb3K4Mw" Message-Id: <1083559716.5394.29.camel@newkid.milsson.nu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 03 May 2004 06:48:36 +0200 Subject: Re: [gentoo-dev] Re: 2004.2 Feature Requests X-Archives-Salt: 3e709043-86f2-4fa3-a6d0-d776de2a3a3b X-Archives-Hash: 63199edd9c2b6df53401f63e40077f5a --=-oZY73FstZXZiUvb3K4Mw Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > All package documentation is accessible from http://localhost/doc/ in the= =20 > default apache configuration files. What about /usr/share/doc/, /usr/share/man/ and /usr/share/info/? app-text/man2html and app-text/info2html seems to be the right tools. /usr/share/doc/ would need ebuild support to be converted to html though. my system has 361 dirs in /usr/share/doc/ of which 68 has a html/ subdir. > > Move away from the filesystem database that portage currently uses to > > something with a bit more perfomance... mysql, sqlite even postgres... = An > > SQL backend interface would be WONDERFUL. >=20 > The biggest problem is that the ebuilds can only be parsed using bash. If= that=20 > restriction can be lifted (by restricting / changing the ebuild format)=20 > parsing should go a lot faster. Really the installed package database is = not=20 > the problem. It seems that a lot of the information in ebuilds could be stated declarative rather than imperative as it is now. Changing the ebuild format to xml could be beneficial. The imperative sections could remain and then fed to bash as the result of an xslt transformation. I see no reason why portage couldn't support two formats in a transition period. A small performance/space improvement would be to keep one file per package rather then by version. > I see what you mean. There are two problems. It is very hard to make a=20 > progress bar as using useflags means that we cannot give a good idea of t= he=20 > amount of code to be compiled in total. Even measuring what has allready = been=20 > done is hard. Also removing the build output creates much problems for=20 > bug-hunting. This is not a portage issue. Make could be patched to calculate the amount of code (in kb) that would be considered for a particular target. I have no idea what kind of overhead we are talking about here though. -John --=-oZY73FstZXZiUvb3K4Mw Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAlc8k0GAlrvwEkG4RAjOMAJ9V2Y8J5E1n7iVwFvERSjpJyYiaCwCeO2vu YD2h90nN6PlyUv8lnqdVono= =mIvc -----END PGP SIGNATURE----- --=-oZY73FstZXZiUvb3K4Mw--