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 1I7Ucf-0004Nu-Th for garchives@archives.gentoo.org; Sun, 08 Jul 2007 11:08:14 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l68B70Hk010231; Sun, 8 Jul 2007 11:07:00 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 l68B3jRB005470 for ; Sun, 8 Jul 2007 11:03:45 GMT Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 11A8564CFA for ; Sun, 8 Jul 2007 11:03:45 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: 0.73 X-Spam-Level: X-Spam-Status: No, score=0.73 required=5.5 tests=[AWL=-0.523, RCVD_NUMERIC_HELO=1.253] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HCoBSgdnwQ+o for ; Sun, 8 Jul 2007 11:03:42 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 2CEA664A65 for ; Sun, 8 Jul 2007 11:03:41 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1I7UYD-0006aH-3d for gentoo-dev@gentoo.org; Sun, 08 Jul 2007 13:03:37 +0200 Received: from 82.153.197.143 ([82.153.197.143]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 08 Jul 2007 13:03:37 +0200 Received: from slong by 82.153.197.143 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 08 Jul 2007 13:03:37 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Steve Long Subject: [gentoo-dev] Re: automated extended information gathering Date: Sun, 08 Jul 2007 12:04:52 +0100 Message-ID: References: <200707071743.44605.vapier@gentoo.org> <200707072356.33088.vapier@gentoo.org> <8cd1ed20707072142y7c029135y6aef76aaee7ae2f3@mail.gmail.com> <200707080101.53131.vapier@gentoo.org> <8cd1ed20707072212o61ee7014gee5a6e5c503c0535@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: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 82.153.197.143 User-Agent: KNode/0.10.4 Sender: news X-Archives-Salt: f0131faf-a8d2-4252-92ce-a2887e605cf4 X-Archives-Hash: 3fec5f204c9017aeb87fcc0197e06b0a Kent Fredric wrote: > On 7/8/07, Mike Frysinger wrote: >> often times when i get a bug report about certain packages, there's >> information about that package that i usually ask for ... i wonder if >> this can be automated >> > 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 >> > } >> Sorry to have skipped the rest of this fascinating discussion, but all I want to know is does the above fulfil the original criteria? I'm guessing it does, since the pkgInfo() function ``trumped it all." >> > 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. >> hmm sounds a bit complex to me. "Abstract designs are simple." But hey, there appear to be loads of 3 line functions all over the shop.. >> the claim i'm making is that there generally isnt any code/checks worth >> adding to ebuilds that would be useful for the purpose of an ebuild I think the intent was for the maintainer to decide what to put there? >> diagnosing >> itself to determine whether it is broken and how it is broken. we just >> dont have a language yet to properly describe the process of diagnosing >> and fixing >> oneself. a fun thesis for an AI doctorate :p Er no a fun project for a noob programmer in a VVHLL. An interesting project would be to make a semantic map of all the terms you guys have finally settled on for the portage API, and then tie that into linguistic analysis (and perhaps even consider i18n for portCore?) all that other stuff you were thinking of, yadda yadda. Have you got a PhD yet? ;P /me runs to pub Er ofc it's not my trademark... *sheesh*. But I'll claim it if you lot don't hurry up. -- gentoo-dev@gentoo.org mailing list