1 |
On Sun, 14 Oct 2001 16:37:23 -0400 |
2 |
Blue Lizard <webmaster@×××××××××.com> wrote: |
3 |
|
4 |
> bugzilla _could_ handle this, but while it is technically ready enough |
5 |
> our development team is in no way prepared to handle the influx of new |
6 |
> users that would find it a pain in the neck to use. |
7 |
|
8 |
Then we find something that's easier to use. We really want this to |
9 |
further Gentoo development, not hamper it. I do not think our current |
10 |
system with sporadic mails to the gentoo-dev (and sometimes |
11 |
gentoo-ebuild!) list is good enough. |
12 |
|
13 |
> A good way for ebuild to handle apps that dont flag/opt well would be |
14 |
> nice, other than hard coding everything :) Like if a build is known to |
15 |
> spark out when a given portion is compiled -O3, knock it down to -O2 |
16 |
> (IOW ebuild parses out flags in make.conf and handles wisely, according |
17 |
> to the writers instructions.) |
18 |
|
19 |
We already do this some places, but it is tricky and highly error-prone |
20 |
since it sometimes requires large amounts of bash wizardry. (Look for -Ox |
21 |
where x > 2, then bump down to two. If x is s, then remove -Ox altogether, |
22 |
etc). |
23 |
|
24 |
Then again, the bash wizardry is what we're (not) paid to do. It's just |
25 |
that I abhor having to maintain tricky code. The tricky part should be |
26 |
getting the code to be easy to write an maintain, not making tricky code |
27 |
out of relatively simple problems. </rant> |
28 |
|
29 |
> > 4) In a related note, we should have a |
30 |
> > "grace-period"/"codeslush"/"codefreeze" of at least one week where we |
31 |
do |
32 |
> > not add new stuff, and do nothing but bug-squashing. We should verify |
33 |
that |
34 |
> > *all* ebuilds have been tested, preferrably with *all* their optional |
35 |
USE |
36 |
> > arguments. |
37 |
> |
38 |
> You are out of your mind. One week? DUDE! This is a 1.0 release of |
39 |
> what could be a major mainstream linux distribution. One week? |
40 |
|
41 |
"at least" should be taken to mean "at minimum", "no less than", or |
42 |
"certainly more wouldn't hurt" ;p |
43 |
|
44 |
> Yes, and the idea is that up until the very minute that feature freeze |
45 |
> goes into effect, anything and everything goes on that list. Someone |
46 |
> gets the slightest little notion of something that'd be cool and POOF!, |
47 |
> on the list. Just that stuff more whimish than others would be in a |
48 |
> diff priority class for obvious reasons. |
49 |
|
50 |
Exactly why I started the wishlist thread, and why I now intend to |
51 |
maintain a wishlist on our site. |
52 |
|
53 |
> Who is in charge of evangelism and propoganda right now? |
54 |
|
55 |
No one in particular, but drobbins is using his connections with IBM's |
56 |
DeveloperWorks for all it's worth. The rest of the developers are of |
57 |
course plugging Gentoo whenever (in)appropriate. |
58 |
|
59 |
|
60 |
Kind regards, |
61 |
|
62 |
Karl T |