Gentoo Archives: gentoo-dev

From: "Harald van Dijk" <truedfx@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: Re: Re: When will KDE 3.5 be marked as stable?
Date: Fri, 05 May 2006 08:10:54
Message-Id: 20060505080354.GA13723@gentoo.org
In Reply to: [gentoo-dev] Re: Re: Re: When will KDE 3.5 be marked as stable? by Bart Braem
1 On Fri, May 05, 2006 at 09:20:08AM +0200, Bart Braem wrote:
2 > Michael Kirkland wrote:
3 >
4 > > I think the problem is that Gentoo is falling into the same sandtrap the
5 > > Debian project has been mired in forever. "arch" and "~arch" are
6 > > polarizing into "stable, but horribly out of date", and "maybe it will
7 > > work".
8 > >
9 > > This leads to people trying to maintain a
10 > > frankenstinian /etc/portage/package.keywords file, constantly adding to it
11 > > and never knowing when things can be removed from it.
12 > >
13 > > I would suggest opening a middle ground tag, where things can be moved to
14 > > from "~arch" when they work for reasonable configuration values, but still
15 > > have open bugs for some people.
16 > >
17 > > That way, people who prefer stability over the latest features can run
18 > > "arch", and everyone who bitches about packages being out of date can run
19 > > the middle tag, and "~arch" can be kept for testing.
20 >
21 > I really, really agree here. I know this seems like a flamewar but it is
22 > starting to annoy me. There are several packages that are several months
23 > behind the official releases. I am going to name some of them:
24
25 Disclaimer: I maintain none of the packages you mentioned, so these are
26 possible reasons, there may be other more important reasons that I
27 didn't think of.
28
29 > Firefox 1.5: 5 months (the entire world uses it now, in stable)
30
31 The ebuild itself causes problems with LINGUAS because of a portage bug
32 (or limitation). And on IRC just yesterday two devs complained about
33 Firefox because for one, 1.5 was unacceptably slow, and for another
34 1.5.0.3 took 100% CPU. Additionally, the latest stable is 1.0.8, which
35 was released less than a month ago; the 1.0 versions are still
36 maintained.
37
38 > KDE 3.5.2: 1.5 months (I know our devs get prereleases, so we had this time)
39
40 kdelibs-3.5.2 needed fixes and workarounds for miscompilations and
41 crashes less than a month ago, according to the changelog.
42
43 > Xorg 7: 5 months
44
45 Strange behaviour for some with virtual/x11 being provided when it
46 shouldn't be, causing missing dependencies for other ebuilds, and
47 compilation issues.
48
49 > I know we have a lot of work to do, but I have some concerns. How long are
50 > we going to maintain old packages? KDE 3.4.3 is no longer supported by the
51 > KDE developpers. Firefox extensions for 1.0 are becoming extinct.
52 > You are also getting a lot of work trying to fix bugs in old software. Most
53 > probably you are starting to backport bugfixes, is this the way we want
54 > things to go?
55 > I understand you don't care about how many users you have, Gentoo is not a
56 > bussiness. But if I try to convince users about the current situation that
57 > is hard. I can't explain this, I really can't. My only answer is "put it
58 > in /etc/portage/package.keywords". But that one is growing very fast...
59 > One nice thing for users would be the addition of more metabugs for recent
60 > packages. I'd like to know why some packages are not stable, and I am not
61 > the only one. Adding a metabug instead of closing all requests for
62 > stabilization with wontfix/wontresolve is much more userfriendly.
63
64 Searching for open and recently closed bugs about the packages in
65 question can help a lot in figuring out reasons packages aren't
66 marked stable. As for metabugs, they would help if the package
67 maintainers feel software is almost ready to go stable and just want to
68 finish up the remaining issues, but in other cases, why? How does it
69 help?
70
71 > Once again, I love to use Gentoo but I don't understand the current
72 > situation. I have the feeling that I'm not the only user so I posted these
73 > comments in order to discuss them. Hopefully you don't mind trying to
74 > explain it all...
75 >
76 > Bart
77 --
78 gentoo-dev@g.o mailing list