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 1I7P7R-0002ox-H0 for garchives@archives.gentoo.org; Sun, 08 Jul 2007 05:15:37 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l685EeoX004086; Sun, 8 Jul 2007 05:14:40 GMT Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l685CkhH001864 for ; Sun, 8 Jul 2007 05:12:46 GMT Received: by py-out-1112.google.com with SMTP id d32so1433042pye for ; Sat, 07 Jul 2007 22:12:46 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=P1GuvXkl/l/cFc+MQ4F22oibppT2FhF7zZRd0tktkx+HrAVq+cq3UJsVju4cegw42tvHB3MTTsDn+YCsGLveyJOGxDg2IFBLVDJFQoBLIdc5IWfHCmwuN8mefcBA3bC7IQrULRR8oXfllOeDNv5ERIQGgRE+7TZSZKeF9Dj6Vkw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=C55uhX+xqvRIi3kyjvyeWe3HzAS0WZWbkUk8Yb4eAg43sohWkQheNVIipoGxh1jR3y0ctLgBxn+8/vLJ06/fzJtuQNaWuaiJvT9t+qkaPKnd7o4VW+ZnZgj+kvhWP7wQrqFbj4AJDNpZvgrqdrgv/qdXbQ9Me3B9aBkD0TK8QsE= Received: by 10.64.210.3 with SMTP id i3mr2595465qbg.1183871565907; Sat, 07 Jul 2007 22:12:45 -0700 (PDT) Received: by 10.64.251.15 with HTTP; Sat, 7 Jul 2007 22:12:45 -0700 (PDT) Message-ID: <8cd1ed20707072212o61ee7014gee5a6e5c503c0535@mail.gmail.com> Date: Sun, 8 Jul 2007 17:12:45 +1200 From: "Kent Fredric" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] automated extended information gathering In-Reply-To: <200707080101.53131.vapier@gentoo.org> 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; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200707071743.44605.vapier@gentoo.org> <200707072356.33088.vapier@gentoo.org> <8cd1ed20707072142y7c029135y6aef76aaee7ae2f3@mail.gmail.com> <200707080101.53131.vapier@gentoo.org> X-Archives-Salt: d296fddc-7da6-41a3-bbc4-c72709e2369a X-Archives-Hash: 2892beacabebf1c586c0d77e9379feed On 7/8/07, Mike Frysinger wrote: > 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 adding > to ebuilds that would be useful for the purpose of an ebuild 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 > -mike > 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 The idea was to place the code to provide that information into the applications pkg_getinfo() section, nothing major, just version numbers etc, and possibly code to test for scenarios that are known to exist but theres currently no known way to fix them. Some of these basic checks can be as simple as grabbing the files CONTENTS out of edb, and checking all the files listed in it exist, and are of the right type ( cat CONTENTS | tr "\n" "\0" | xargs -iSTR -0 file STR ), and arn't symlinks that don't go anywhere, you know, the usual sort of bugs that flare up as a result of user interaction ;)) The output of those checks are still going to be want to be read and interpreted by a human, but the more you know of a situation, the more you have to find the bug with. -- Kent ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x| print "enNOSPicAMreil kdrtf@gma.com"[(2*x)..(2*x+1)]}' -- gentoo-dev@gentoo.org mailing list