1 |
Hello Kent, |
2 |
|
3 |
Friday, August 8, 2014, 9:29:54 PM, you wrote: |
4 |
|
5 |
But it's possible to fix many problems even now! |
6 |
|
7 |
What would you tell if something VERY simple is implemented like - reporting |
8 |
every emerge failed due to slot conflict back home with details for inspection? |
9 |
|
10 |
If maintainers had that kind of data then they could learn from the wild. I don't know what |
11 |
they would learn but I know it would be a very useful experience that might jump start |
12 |
evolution - useful updates to emerge and other tools. Almost every system designed by nature has |
13 |
feedback functions. It's the safe update - it will work even if not optimal from the start |
14 |
or even if it's not clear what it will help to learn. The quality of ebuilds would improve too. |
15 |
|
16 |
And from the useful life database new tools could evolve like - bug reporting automatization a |
17 |
whole new world of tool. |
18 |
|
19 |
http://db.gentoo.org/report/ |
20 |
|
21 |
System: System name |
22 |
Arch: |
23 |
Package emerged: .... |
24 |
Environment: .... |
25 |
Dependency graph: .... -> ... -> ... |
26 |
Fail message: |
27 |
|
28 |
* 3 reports per day are accepted from one single IP |
29 |
* no dups |
30 |
|
31 |
http://db.gentoo.org/stats/ |
32 |
|
33 |
- SlickGrid stats |
34 |
|
35 |
Arch Package How many times Failed Fail message |
36 |
|
37 |
Click on Package -> Dependency Graph |
38 |
|
39 |
If GENTOO had everything emerging from any state (goal unattainable but desirable) that |
40 |
would be a great advantage for the users. That feel of a lean mean machine that saves time - it's |
41 |
tasty - new fans warranted. |
42 |
|
43 |
|
44 |
|
45 |
On 9 August 2014 04:58, Igor <lanthruster@×××××.com> wrote: |
46 |
Maintainers have no feedback from their ebuilds, they all do their best but there are no tools |
47 |
to formalize their work. No compass. They have no access to user |
48 |
space where the packages are installed, unaware how users are using their ebuilds. It's the design |
49 |
failure that hunts Gentoo from the start - no global intellectual bug tracking system. Doing not mistakes |
50 |
- not possible, the automated tracking sub-systems should be there but... we are where we are. |
51 |
Some of that is doable, ie: we could have installation metrics systems like CPAN has a testers network with a matrix showing where a given thing is failing : http://matrix.cpantesters.org/?dist=CPAN-Meta-Requirements%202.126 |
52 |
|
53 |
But its a lot of work investment to support. |
54 |
|
55 |
And beyond "it installs" and "its tests pass", its piratically infeasible to track software failing beyond there. |
56 |
|
57 |
And some of the reasons we have dependency declarations are to avoid problems that will ONLY be seen at runtime and WONT be seen during installation or testing. ( Usually because the problem was found before there were tests for it ) |
58 |
|
59 |
For that, only manual feedback systems, such as our present bugzilla, are adequate. |
60 |
|
61 |
|
62 |
-- |
63 |
Kent |
64 |
|
65 |
KENTNL - https://metacpan.org/author/KENTNL |
66 |
|
67 |
|
68 |
|
69 |
|
70 |
|
71 |
-- |
72 |
Best regards, |
73 |
Igor mailto:lanthruster@×××××.com |