Chris Gianelloni wrote:
> On Sat, 2006-09-02 at 23:11 -0600, Ryan Hill wrote:
>> I'd have to agree with you on that. I understand the appeal of
exciting press releases but there were over 75 GCC 4.1 bugs still open
for problems in *~arch* when the decision was made to go stable. Even
now ther
Chris Gianelloni wrote:
> On Sun, 2006-09-03 at 07:41 +, Wiktor Wandachowicz wrote:
>> its developers. Edgar's call was targeted mostly at releng and QA teams, who
>> should poke developers to decrease number of similar problems.
>
> Sorry, but Release Engineering has no wishes to become the "
On Sun, 2006-09-03 at 07:41 +, Wiktor Wandachowicz wrote:
> its developers. Edgar's call was targeted mostly at releng and QA teams, who
> should poke developers to decrease number of similar problems.
Sorry, but Release Engineering has no wishes to become the "Gentoo
Developer Babysitting Pro
On Sat, 2006-09-02 at 23:11 -0600, Ryan Hill wrote:
> Carsten Lohrke wrote:
>
> > we're understaffed, partly - and this is my very personal opinion - the
> > problem is that releasing with GCC 4.x has been rushed
>
> I'd have to agree with you on that. I understand the appeal of exciting
> pre
On Sunday 03 September 2006 15:02, Carsten Lohrke wrote:
> You're wrong here. What I'm inclined about is that we had (leastwise) a
> fourteen day short notice to when the releaase snapshot would be taken. To
> the end of this time frame there was another one that we'd release with GCC
> 4.x. Even i
On Sunday 03 September 2006 00:42, Diego 'Flameeyes' Pettenò wrote:
> And waiting other 2, 3, 4, 5, 6 months won't change the thing. Why? Because
> we have _no_ accessibility team right now.
Well, the bug is assigned to williamh, who is not /completely/ inactive. I
wonder, if only 37 commits in
Either MTA or MUA brokeness. Another email I have to send a second time. :(
On Sunday 03 September 2006 00:42, Diego 'Flameeyes' Pettenò wrote:
> And waiting other 2, 3, 4, 5, 6 months won't change the thing. Why? Because
> we have _no_ accessibility team right now.
Well, the bug is assigned to
Wiktor Wandachowicz wrote:
>> If the users are too lazy to read the documentation, why should we care
>> about them?
>
> Because we risk that Gentoo may receive the "user-UN-friendly" label and
> become irrelevant in the long run? I know it ain't gonna happen, but still.
Well, that might be the c
Luis Francisco Araujo wrote:
>
> If neither of those points are convincing enough, then remember free
> software comes with *NO-WARRANTY*
s/free//
Even payware is w/out warranties.
lu
--
Luca Barbato
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
--
gentoo-dev@gentoo.org mailing l
Wiktor Wandachowicz wrote:
Simon Stelling wrote:
Edgar Hucek wrote:
I know my tools but not necessarly the normal user who wanna use gentoo
and is ending frustrated.
If the users are too lazy to read the documentation, why should we care
about them?
Because we risk that Gentoo may receive t
Simon Stelling wrote:
> Edgar Hucek wrote:
> > I know my tools but not necessarly the normal user who wanna use gentoo
> > and is ending frustrated.
>
> If the users are too lazy to read the documentation, why should we care
> about them?
Because we risk that Gentoo may receive the "user-UN-frie
Carsten Lohrke wrote:
we're understaffed, partly - and this is my very personal opinion - the
problem is that releasing with GCC 4.x has been rushed
I'd have to agree with you on that. I understand the appeal of exciting
press releases but there were over 75 GCC 4.1 bugs still open for
prob
On Sunday 03 September 2006 00:16, Carsten Lohrke wrote:
> Neither Gnome nor KDE (no use flag in this case) accessibiliy stuff builds
> now - and bug 116030 is open since nine months.
And waiting other 2, 3, 4, 5, 6 months won't change the thing. Why? Because we
have _no_ accessibility team right
Seems my message got swallowed...
On Saturday 02 September 2006 15:36, Edgar Hucek wrote:
> Just a side hint. Try to enable all flags at the first cimpile time would
> reduce trys drasticaly ;)
There are lots of use flag combinations incompatible with each other within a
package as well as packa
On Sat, Sep 02, 2006 at 08:55:33AM -0500, Mike Doty wrote:
> If that's not good enough for you, please find a distribution that you
> have to pay for like RHEL. Their testing is no better than ours, but
> at least paying something entitles you to bitch at them.
Or consider paying a Gentoo develope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Edgar Hucek wrote:
> Danny van Dyk schrieb:
>> Am Samstag, 2. September 2006 13:18 schrieb Edgar Hucek:
> 2.) Enable the use flage accessibility gnome cant be
> merged. It fails on compile the speech-tools.
> It seams that USE flags are not
Simon Stelling <[EMAIL PROTECTED]> posted [EMAIL PROTECTED],
excerpted below, on Sat, 02 Sep 2006 16:14:47 +0200:
> Edgar Hucek wrote:
>> I know my tools but not necessarly the normal user who wanna use gentoo
>> and is ending frustrated.
>
> If the users are too lazy to read the documentation,
I know my tools but not necessarly the normal user who wanna use gentoo
and is ending frustrated.
cu
Edgar (gimli) Hucek
Enrico? Is that you in disguise?
--
gentoo-dev@gentoo.org mailing list
Edgar Hucek wrote:
> I know my tools but not necessarly the normal user who wanna use gentoo
> and is ending frustrated.
If the users are too lazy to read the documentation, why should we care
about them?
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing l
Edgar Hucek wrote:
> Danny van Dyk schrieb:
>> This hasn't yet investigated allt he possible combinations of packages
>> depending on dev-lang/php, or the ~10,000 other packages in the tree.
>>
>> Danny
>
> Just a side hint. Try to enable all flags at the first cimpile time would
> reduce trys dr
Simon Stelling schrieb:
> Edgar Hucek wrote:
>> Just a side hint. Try to enable all flags at the first cimpile time would
>> reduce trys drasticaly ;)
>
> If you had a look at the php ebuild (just because we took it as example
> here), you'd see that it is a bit more complicated than just enabling
Edgar Hucek wrote:
> Just a side hint. Try to enable all flags at the first cimpile time would
> reduce trys drasticaly ;)
If you had a look at the php ebuild (just because we took it as example
here), you'd see that it is a bit more complicated than just enabling
everything to have everything tes
On 02/09/06, Edgar Hucek <[EMAIL PROTECTED]> wrote:
Realy funny, i only hear exuses but no real solution for the problem. The universe ending before testing is finished is a pretty good excuse.
Danny van Dyk schrieb:
> Am Samstag, 2. September 2006 13:18 schrieb Edgar Hucek:
2.) Enable the use flage accessibility gnome cant be
merged. It fails on compile the speech-tools.
It seams that USE flags are not realy tested or how
can it happen that there are already know bugs
24 matches
Mail list logo
