Gentoo Archives: gentoo-dev

From: Kent Fredric <kentfredric@×××××.com>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] automated extended information gathering
Date: Sun, 08 Jul 2007 03:34:12
Message-Id: 8cd1ed20707072031n6d4e47c7l4ea616660c6dcefb@mail.gmail.com
In Reply to: Re: [gentoo-dev] automated extended information gathering by Mike Frysinger
1 On 7/8/07, Mike Frysinger <vapier@g.o> wrote:
2 > On Saturday 07 July 2007, Kent Fredric wrote:
3 > > Implementation details wise, I would like to see packages have
4 > > possibly 2 functions,
5 > > 1: Info, and 2: Check.
6 > > Reason Being that you wont be able to fetch installation status info
7 > > on a package thats not installed, and if a package is failing to
8 > > install, you're more likely wanting to check the status of the things
9 > > it depends on, not the package itself.
10 >
11 > i dont really understand what you're going for here ... the point was to get
12 > extended information on things that are installed ... i dont know what you'd
13 > want/expect for trying to query packages that arent installed
14 >
15 > > Check would contain manual tests for a given package, thats either
16 > > installed or not installed ,as well as names of packages to run info
17 > > on.
18 > >
19 > > Info would be more usefull in diagnosing mis-installed packages or
20 > > packages that failed to run properly despite being compiled and
21 > > installed without a hitch ( it happens )
22 >
23 > sounds like you're duplicating the point of src_test() but without any real
24 > way of quantifying it or making it useful to coordinate things ... please
25 > expound on what you're going for because i'm just not seeing it ...
26 > -mike
27 >
28 >
29
30 50% of bugs I tend to see are compile failures.
31
32 Compile Failures are often a result of things that the compile was dependant on.
33
34 Thus, finding info on a given package to understand what its problem
35 is, you should be info-querying its dependants, not the package
36 itself, no?
37
38 Information you want sent to bug reports are related to the software
39 that it depended on, no? ( ie: xine-libs wont compile : emerge --info
40 xine-libs should report information on ffmpeg, which has changed,
41 causing the failure )
42
43 And if xine libs wasnt installed, it would be pointless to report
44 information about xine-libs installation when its not installed
45 becasue it cant be ;)
46
47 So instead of asking the user what version of X dependant they have,
48 emerge --info atom should report that in a standardised way, making
49 them able to provide more relevant information in the initial report
50
51 --
52 Kent
53 ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
54 print "enNOSPicAMreil kdrtf@×××.com"[(2*x)..(2*x+1)]}'
55 --
56 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] automated extended information gathering Mike Frysinger <vapier@g.o>