1 |
On 7/8/07, Mike Frysinger <vapier@g.o> wrote: |
2 |
> On Sunday 08 July 2007, Kent Fredric wrote: |
3 |
> > Ok, I've re-thought some of my ideas and tried to come up with a more |
4 |
> > concise explanation |
5 |
> > with some practical example syntax. The basic concept of 'check' was |
6 |
> > 'this will work even if the package aint installed yet' and info was |
7 |
> > 'for working but bust packages only', but that can be superceded with |
8 |
> > a CHECKLIST and a conditional driven INFO function. |
9 |
> |
10 |
> as they say, the devil is in the details ... |
11 |
> |
12 |
> > pkg_getinfo(){ |
13 |
> > if [[ installed ]]; then |
14 |
> > someSelfCheck; |
15 |
> > someSelfCheck; |
16 |
> > echo someversionNumberStuff; |
17 |
> > fi |
18 |
> > someBasicSystemCheckRequiredForPkgToWork(); |
19 |
> > if [[ someCondition ]]; then |
20 |
> > get_info( some-cat/d-lib ); # its not on the dep list, but we want |
21 |
> > to check its info status as part of /our/ info status. |
22 |
> > fi |
23 |
> > } |
24 |
> |
25 |
> the claim i'm making is that there generally isnt any code/checks worth adding |
26 |
> to ebuilds that would be useful for the purpose of an ebuild diagnosing |
27 |
> itself to determine whether it is broken and how it is broken. we just dont |
28 |
> have a language yet to properly describe the process of diagnosing and fixing |
29 |
> oneself. a fun thesis for an AI doctorate :p |
30 |
> -mike |
31 |
> |
32 |
|
33 |
|
34 |
On 7/8/07, Mike Frysinger <vapier@g.o> wrote: |
35 |
> often times when i get a bug report about certain packages, there's |
36 |
> information about that package that i usually ask for ... i wonder if this |
37 |
> can be automated |
38 |
|
39 |
The idea was to place the code to provide that information into the |
40 |
applications pkg_getinfo() section, nothing major, just version |
41 |
numbers etc, and possibly code to test for scenarios that are known to |
42 |
exist but theres currently no known way to fix them. |
43 |
|
44 |
Some of these basic checks can be as simple as grabbing the files |
45 |
CONTENTS out of edb, and checking all the files listed in it exist, |
46 |
and are of the right type ( cat CONTENTS | tr "\n" "\0" | xargs -iSTR |
47 |
-0 file STR ), and arn't symlinks that don't go anywhere, you know, |
48 |
the usual sort of bugs that flare up as a result of user interaction |
49 |
;)) |
50 |
|
51 |
The output of those checks are still going to be want to be read and |
52 |
interpreted by a human, but the more you know of a situation, the more |
53 |
you have to find the bug with. |
54 |
|
55 |
-- |
56 |
Kent |
57 |
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x| |
58 |
print "enNOSPicAMreil kdrtf@×××.com"[(2*x)..(2*x+1)]}' |
59 |
-- |
60 |
gentoo-dev@g.o mailing list |