| 1 |
On Friday 09 July 2004 19:17, Caleb Tennis wrote: |
| 2 |
> I've been spending my time the past few weeks testing 3.3.0_beta1, not |
| 3 |
> running 3.2.3. |
| 4 |
|
| 5 |
Well someone on the kde team should, right? Or if you rely on user input, |
| 6 |
automatically push new versions from ~x86 to x86 when no user has complained |
| 7 |
(it's easier to complain than to state "everything works fine", especially |
| 8 |
when you don't use all of kde, I personally would never find a problem with |
| 9 |
kdegames as I don't install it). But I do use kdepim and if I find a problem |
| 10 |
with it I report it to the KDE bug system. However, I have not found any |
| 11 |
error that was the ebuilds fault. Should I file a bug stating "kdepim merged |
| 12 |
fine and seems to work ok a week after merging"? |
| 13 |
|
| 14 |
> The fact is that, with the way portage is structured and the commands you |
| 15 |
> have to use to properly make the submittals, it takes me well over an hour |
| 16 |
> to bump a version for KDE. |
| 17 |
|
| 18 |
For getting it from ~x86 to x86? If that's really the case then perhaps this |
| 19 |
should open a wider discussion: a) Need more developers as most do have a |
| 20 |
real life besides gentoo or b) make it simpler! |
| 21 |
|
| 22 |
> Considering the fact that it's volunteer time on my part, it gets put down |
| 23 |
> on my priority list. |
| 24 |
|
| 25 |
Then its the job of someone who does get paid to make it easier for the |
| 26 |
volunteers to get the job done, right? |
| 27 |
|
| 28 |
> So, if you want to be part of the solution, start being proactive in |
| 29 |
> helping to fix bugs and get ebuilds submitted. |
| 30 |
|
| 31 |
The ebuild is almost always there when I want to upgrade a package it just |
| 32 |
sits in ~x86 ... |
| 33 |
|
| 34 |
> and it gets to be a bit frustrating to have to try and explain over and over |
| 35 |
> again. |
| 36 |
|
| 37 |
Have a standard reply to paste, also stating you just don't have the time to |
| 38 |
answer everyone personally. Its still better than saying nothing because |
| 39 |
you're overworked. In the time you explain this to all of those people you |
| 40 |
could move lots of packages to x86 :) |
| 41 |
|
| 42 |
> That said, there's absolutely no harm in kde sitting as ~x86 for 3.2.3. |
| 43 |
> It's still completely installable, and portage is configurable enough so as |
| 44 |
> to not complain to you to downgrade. |
| 45 |
|
| 46 |
Yes there is harm in it. When I first see a package in ~x86 after the official |
| 47 |
release I think there might be a problem with it and don't merge it until I |
| 48 |
can't stand it any more and just merge it as I want to have a fix for all the |
| 49 |
bugs I reported for the last version of kde :) |
| 50 |
|
| 51 |
Still, if I just edit the various files in /etc/portage/ I might at some time |
| 52 |
get a really unusable version of an ebuild which would not be the case if the |
| 53 |
build sat in ~x86 for a week or so before going to x86. |
| 54 |
|
| 55 |
I really thought that an ebuild automatically went to x86 after some time of |
| 56 |
no complaints, until now... |
| 57 |
|
| 58 |
All that being said, I do understand that you all have a real life, work and |
| 59 |
family to attend to. Maybe gentoo should get more developers and skip ~x86 |
| 60 |
until they have :) I would really like to help besides reporting a bug or two |
| 61 |
once in a while, if it wasn't so much work. What good would I do when all I |
| 62 |
could spend was and hour or two every few days. Or a whole day once in a |
| 63 |
while and then nothing for a week? |
| 64 |
|
| 65 |
|
| 66 |
Alex |
| 67 |
|
| 68 |
-- |
| 69 |
gentoo-dev@g.o mailing list |
Archives