From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1I7Owk-0004V2-4w for garchives@archives.gentoo.org; Sun, 08 Jul 2007 05:04:34 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l6852sG9028881; Sun, 8 Jul 2007 05:02:54 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l684xTjS022827 for ; Sun, 8 Jul 2007 04:59:30 GMT Received: from ip6-localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 39E4565214 for ; Sun, 8 Jul 2007 04:59:29 +0000 (UTC) From: Mike Frysinger Organization: wh0rd.org To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] automated extended information gathering Date: Sun, 8 Jul 2007 01:01:52 -0400 User-Agent: KMail/1.9.7 References: <200707071743.44605.vapier@gentoo.org> <200707072356.33088.vapier@gentoo.org> <8cd1ed20707072142y7c029135y6aef76aaee7ae2f3@mail.gmail.com> In-Reply-To: <8cd1ed20707072142y7c029135y6aef76aaee7ae2f3@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1217973.WuAbDPy20G"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200707080101.53131.vapier@gentoo.org> X-Archives-Salt: 318ece27-777c-4d27-b06b-13da57324186 X-Archives-Hash: f74b3d7d8b3538d4db475974b7ac1e62 --nextPart1217973.WuAbDPy20G Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 08 July 2007, Kent Fredric wrote: > Ok, I've re-thought some of my ideas and tried to come up with a more > concise explanation > with some practical example syntax. The basic concept of 'check' was > 'this will work even if the package aint installed yet' and info was > 'for working but bust packages only', but that can be superceded with > a CHECKLIST and a conditional driven INFO function. as they say, the devil is in the details ... > pkg_getinfo(){ > if [[ installed ]]; then > someSelfCheck; > someSelfCheck; > echo someversionNumberStuff; > fi > someBasicSystemCheckRequiredForPkgToWork(); > if [[ someCondition ]]; then > get_info( some-cat/d-lib ); # its not on the dep list, but we want > to check its info status as part of /our/ info status. > fi > } the claim i'm making is that there generally isnt any code/checks worth add= ing=20 to ebuilds that would be useful for the purpose of an ebuild diagnosing=20 itself to determine whether it is broken and how it is broken. we just don= t=20 have a language yet to properly describe the process of diagnosing and fixi= ng=20 oneself. a fun thesis for an AI doctorate :p =2Dmike --nextPart1217973.WuAbDPy20G Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (GNU/Linux) iQIVAwUARpBvwUFjO5/oN/WBAQKBUg/5AdhB1kge1k/W7HVozk3+Qpyr2cGRDa9A DDS+u7ceAs1H/IL4HFrj+Q25bCvBedrbbTZ6DOeXEGvzombamo1Wqzipo+G7D5A2 6EzB+NxB8Zoa2gYVhYmHk8aHzLVsc0WdJ81L4DJscwaxP34MRlgnTGAUMoIw9xO/ AQjQhSaAz6FpS6he/QpDesBqtCLYqSEttCT8E4GIo8wsjg+1RJGqvJS37WEW5DW9 q5cDuJPBV9/uiLGPT+uHK6aSICye2JznzvqmIHPLkpi2ptWRRLmIyPShHgKWOF+a ADDER1Azim0zJiSirc4AetkwOEAuKiMdkTxI98e6/lPt7NPSDSIEflTDiNg5I/oL Mr9fgygSZrrlBOoOSx3N9ImswLgUcsuXKn3bLtS8AA7WCiVfA2RhKSSfnq8rIIGR TtjyzwphB67pw5Xtn6WsLY1Lys0V9TJKgu5mjAPzjWh67iI/jPaq0T5GjHBP/7IT vRyvuIa+G/sc34qv7jb/pRi01hRaGpevOMuAncTWFhzkFHnAFOCNFHUv7fdxQkRo uelsK20AFUeuTk9pA+E6hP8G5H3/Gn0z462igIy/pgx30QW3He2rjaPwQurALWFk VE40/Sz/CxsSMQ16101O7Hlz0Ka4cWDMmLRmaLPEbynTuh/KP8UzVHS8F5Cw7XRK GJRbNEFz158= =6zzc -----END PGP SIGNATURE----- --nextPart1217973.WuAbDPy20G-- -- gentoo-dev@gentoo.org mailing list