1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Saturday 06 September 2003 7:05 pm, David Sankel wrote: |
5 |
> Hello gentoo developers, |
6 |
> |
7 |
> I would like to say great job to all of you. Gentoo is an exceptional |
8 |
> distribution. I have been using it for about 7 months now. You all |
9 |
> should be very proud of yourselves for creating a very solid software |
10 |
> product. |
11 |
> |
12 |
> I am an independent contractor with several years experience in user |
13 |
> interaction with software systems. I came up with a few suggestions for |
14 |
> the gentoo system. It is my hope that you will find them interesting or |
15 |
> informative. |
16 |
> |
17 |
> 1) etc-update changes for a more automated system update |
18 |
> |
19 |
> etc-update allows you to automatically update (noted) etc files that one |
20 |
> never changed from their last emerge. This could save a lot of |
21 |
> maintenance time if it was put in a cron job to routinely do that after |
22 |
> an "emerge sync;emerge -u world" |
23 |
> The user then wouldn't have to look at all of the etc files to see |
24 |
> if they were changed after every "emerge sync; emerge-u world". |
25 |
|
26 |
You can't be serious!? If you don't examine those etc-update changes you could |
27 |
seriously screw up your system. |
28 |
|
29 |
> 2) make.conf updates to be more automated |
30 |
> |
31 |
> Most gentoo users, I believe, modify this file. This specific file changes |
32 |
> quite often with updates. Since most users only modify the "USE" and |
33 |
> "CFLAGS" components, having an update that is automatic is plausible. This |
34 |
> feature is a trade off between the integrity and consistency of the system |
35 |
> verses end-user maintenance time. |
36 |
|
37 |
What about those of use with a load of other stuff in there. I just use the |
38 |
interactive merge function of etc-update. Takes about 30 seconds to do |
39 |
make.conf. |
40 |
|
41 |
> |
42 |
> 3) emerge -u world "NOTICE:" output changes. |
43 |
> |
44 |
> When doing an "emerge -u world" several "NOTICE:"'s fly by on the screen. |
45 |
> For many users, they go unread although they contain important information |
46 |
> in a lot of cases. If these "NOTICE:"'s are cached and output at the end |
47 |
> of an "emerge -u world", their readership would have a dramatic increase. |
48 |
> This would allow interested gentoo users to be more informed of their |
49 |
> system. |
50 |
|
51 |
I believe their is a patch to do this somewhere around. Sorry I can't remember |
52 |
where. |
53 |
|
54 |
> 4) emerge -u world progress bar option |
55 |
> |
56 |
> Most users probably care less about the compilation stages of their update |
57 |
> in comparison to the percentage of completion. A progress bar in this |
58 |
> area would be a nice aesthetic and informative addition for most users. |
59 |
> In order for this to happen, the output of the "emerge -u world" command |
60 |
> would probably have to be standardized with some flags to mark the |
61 |
> beginning and end of a compile. |
62 |
|
63 |
A progress bar would be difficult as its difficult to estimate how much code |
64 |
is left to compile and/or how long that is going to take. It would probably |
65 |
end up just saying 20 our of 24, 21 out of 24 etc. I personally prefer to see |
66 |
the compilation so when it breaks I can see exactly where it was before it |
67 |
broke. |
68 |
|
69 |
> 5) A simple graphical front end to maintenance commands such as "emerge |
70 |
> sync", "emerge -u world", and "etc-update". |
71 |
> |
72 |
> It would be a nice feature if users didn't have to commit these commands |
73 |
> to memory for regular maintenance. The maintenance menu might have an |
74 |
> icon on all of the default desktops. If this type of program was |
75 |
> implemented, it could be prominently displayed and made known for all new |
76 |
> users. Perhaps the install documentation could use this tool as much as |
77 |
> possible. |
78 |
|
79 |
Well, there are programs whcih do some of the stuff you might be referring to |
80 |
like kportage. They don't work on all desktops though, and they don't do all |
81 |
of that. |
82 |
|
83 |
> 6) A streamlined GUI install. |
84 |
> |
85 |
> I'm sure this one has been brought up before. I consider this the "1.0" |
86 |
> maker of the gentoo distribution. In such an installer, I suggest that |
87 |
> the CFLAGS should not be modified by default. It has been shown in |
88 |
> several places that optimizing these does not give a significant enough |
89 |
> performance increase. It should stay, of course, as an option though. |
90 |
|
91 |
Your right, GUI discussion is all over the place. It would be useful to some |
92 |
users certainly. |
93 |
|
94 |
What places? Not modifying the CFLAGS? What do you suggest they should be left |
95 |
at. I can assure you, your Athlon XP 2800+ or whatever will comparitivly |
96 |
crawl with mcpu=i686. |
97 |
|
98 |
> 7) Emerge -S and Emerge -s speed improvements. |
99 |
> |
100 |
> I don't know why these commands perform as slow as they do. My intuition |
101 |
> says that they could be an order of magnitude faster. Perhaps a |
102 |
> reimplementation in C/C++ or a data format change could help. |
103 |
|
104 |
Their are faster versions. http://bugs.gentoo.org/show_bug.cgi?id=24756 for |
105 |
example. |
106 |
|
107 |
> Thanks for reading my comments and taking them into consideration. Again, |
108 |
> I want to thank you, the gentoo developers, for doing such a great job on |
109 |
> the gentoo system. I welcome any thoughts or comments on my suggestions |
110 |
> in this newsgroup or otherwise. |
111 |
> |
112 |
> Sincerely, |
113 |
> |
114 |
> David J. Sankel |
115 |
> |
116 |
> camio@×××××.com |
117 |
> |
118 |
> |
119 |
> -- |
120 |
> gentoo-dev@g.o mailing list |
121 |
|
122 |
Puggy |
123 |
-----BEGIN PGP SIGNATURE----- |
124 |
Version: GnuPG v1.2.2 (GNU/Linux) |
125 |
|
126 |
iD8DBQE/WjO1XYnvgFdTojMRAn/uAKCbyE9q3OSY2E6Ckqgr+XTt81hcMwCgrN4C |
127 |
VbMZGO4LLKRHVCGcNHr+5WY= |
128 |
=bZ0l |
129 |
-----END PGP SIGNATURE----- |
130 |
|
131 |
|
132 |
-- |
133 |
gentoo-dev@g.o mailing list |