On 7/8/07, Mike Frysinger <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]"[(2*x)..(2*x+1)]}'
--
[EMAIL PROTECTED] mailing list
