From: "Harald van Dijk" <truedfx@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Re: Re: When will KDE 3.5 be marked as stable?
Date: Fri, 5 May 2006 10:03:54 +0200 [thread overview]
Message-ID: <20060505080354.GA13723@gentoo.org> (raw)
In-Reply-To: <e3eub8$fcr$1@sea.gmane.org>
On Fri, May 05, 2006 at 09:20:08AM +0200, Bart Braem wrote:
> Michael Kirkland wrote:
>
> > I think the problem is that Gentoo is falling into the same sandtrap the
> > Debian project has been mired in forever. "arch" and "~arch" are
> > polarizing into "stable, but horribly out of date", and "maybe it will
> > work".
> >
> > This leads to people trying to maintain a
> > frankenstinian /etc/portage/package.keywords file, constantly adding to it
> > and never knowing when things can be removed from it.
> >
> > I would suggest opening a middle ground tag, where things can be moved to
> > from "~arch" when they work for reasonable configuration values, but still
> > have open bugs for some people.
> >
> > That way, people who prefer stability over the latest features can run
> > "arch", and everyone who bitches about packages being out of date can run
> > the middle tag, and "~arch" can be kept for testing.
>
> I really, really agree here. I know this seems like a flamewar but it is
> starting to annoy me. There are several packages that are several months
> behind the official releases. I am going to name some of them:
Disclaimer: I maintain none of the packages you mentioned, so these are
possible reasons, there may be other more important reasons that I
didn't think of.
> Firefox 1.5: 5 months (the entire world uses it now, in stable)
The ebuild itself causes problems with LINGUAS because of a portage bug
(or limitation). And on IRC just yesterday two devs complained about
Firefox because for one, 1.5 was unacceptably slow, and for another
1.5.0.3 took 100% CPU. Additionally, the latest stable is 1.0.8, which
was released less than a month ago; the 1.0 versions are still
maintained.
> KDE 3.5.2: 1.5 months (I know our devs get prereleases, so we had this time)
kdelibs-3.5.2 needed fixes and workarounds for miscompilations and
crashes less than a month ago, according to the changelog.
> Xorg 7: 5 months
Strange behaviour for some with virtual/x11 being provided when it
shouldn't be, causing missing dependencies for other ebuilds, and
compilation issues.
> I know we have a lot of work to do, but I have some concerns. How long are
> we going to maintain old packages? KDE 3.4.3 is no longer supported by the
> KDE developpers. Firefox extensions for 1.0 are becoming extinct.
> You are also getting a lot of work trying to fix bugs in old software. Most
> probably you are starting to backport bugfixes, is this the way we want
> things to go?
> I understand you don't care about how many users you have, Gentoo is not a
> bussiness. But if I try to convince users about the current situation that
> is hard. I can't explain this, I really can't. My only answer is "put it
> in /etc/portage/package.keywords". But that one is growing very fast...
> One nice thing for users would be the addition of more metabugs for recent
> packages. I'd like to know why some packages are not stable, and I am not
> the only one. Adding a metabug instead of closing all requests for
> stabilization with wontfix/wontresolve is much more userfriendly.
Searching for open and recently closed bugs about the packages in
question can help a lot in figuring out reasons packages aren't
marked stable. As for metabugs, they would help if the package
maintainers feel software is almost ready to go stable and just want to
finish up the remaining issues, but in other cases, why? How does it
help?
> Once again, I love to use Gentoo but I don't understand the current
> situation. I have the feeling that I'm not the only user so I posted these
> comments in order to discuss them. Hopefully you don't mind trying to
> explain it all...
>
> Bart
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-05-05 8:10 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 23:05 [gentoo-dev] When will KDE 3.5 be marked as stable? m h
2006-04-03 23:11 ` Stephen P. Becker
2006-04-03 23:44 ` Aron Griffis
2006-04-04 2:16 ` Kari Hazzard
2006-04-04 2:28 ` Stephen P. Becker
2006-04-04 2:50 ` lnxg33k
2006-04-04 3:23 ` Jason S
2006-04-04 3:37 ` Kari Hazzard
2006-04-04 15:12 ` Stephen P. Becker
2006-04-04 16:11 ` Kari Hazzard
2006-04-04 16:37 ` Stephen P. Becker
2006-04-04 17:04 ` m h
2006-04-04 17:42 ` Phil Richards
2006-04-04 21:05 ` Paul de Vrieze
2006-04-04 21:09 ` Paul de Vrieze
2006-04-04 20:55 ` Paul de Vrieze
2006-04-04 16:42 ` Simon Stelling
2006-04-04 20:52 ` Paul de Vrieze
2006-04-04 2:37 ` Grant Goodyear
2006-04-04 12:05 ` Carsten Lohrke
2006-04-04 9:21 ` Michael Cummings
2006-04-04 9:42 ` Jan Kundrát
2006-04-04 10:38 ` Michael Cummings
2006-04-03 23:13 ` Diego 'Flameeyes' Pettenò
2006-04-03 23:25 ` m h
2006-04-04 5:51 ` [gentoo-dev] " Duncan
2006-04-04 6:16 ` Donnie Berkholz
2006-04-04 10:10 ` [gentoo-dev] " Duncan
2006-04-04 6:09 ` [gentoo-dev] " Philip Webb
2006-04-04 6:42 ` Diego 'Flameeyes' Pettenò
2006-04-04 10:28 ` [gentoo-dev] " Duncan
2006-04-04 12:03 ` [gentoo-dev] " Philip Webb
2006-04-04 9:12 ` Chris Bainbridge
2006-04-04 9:51 ` Diego 'Flameeyes' Pettenò
2006-04-04 10:14 ` [gentoo-dev] " Duncan
2006-04-04 10:38 ` Caleb Tennis
2006-04-04 11:17 ` [gentoo-dev] " Duncan
2006-04-04 12:18 ` [gentoo-dev] " Philip Webb
2006-05-04 11:48 ` [gentoo-dev] " Bart Braem
2006-05-04 12:18 ` Chris Gianelloni
2006-05-04 12:30 ` Jeff Rollin
2006-05-05 7:14 ` Philip Webb
2006-05-05 7:35 ` Jakub Moc
2006-05-05 7:56 ` Philip Webb
2006-05-05 8:11 ` Jakub Moc
2006-05-05 9:03 ` Michael Kirkland
2006-05-05 8:16 ` Chris Bainbridge
2006-05-05 20:09 ` Jeff Smelser
2006-05-06 9:03 ` Richard Fish
2006-05-04 12:21 ` Jeff Rollin
2006-05-04 13:45 ` Paul de Vrieze
2006-05-04 14:28 ` Jeff Rollin
2006-05-04 23:29 ` Michael Kirkland
2006-05-05 5:28 ` Jeff Rollin
2006-05-05 10:30 ` [gentoo-dev] " Duncan
2006-05-05 6:32 ` [gentoo-dev] " Kevin F. Quinn (Gentoo)
2006-05-05 11:20 ` Carsten Lohrke
2006-05-05 13:23 ` Kevin F. Quinn (Gentoo)
2006-05-05 14:38 ` Carsten Lohrke
2006-05-05 18:37 ` Kevin F. Quinn (Gentoo)
2006-05-05 19:10 ` Carsten Lohrke
2006-05-05 19:08 ` Chris Gianelloni
2006-05-05 7:20 ` [gentoo-dev] " Bart Braem
2006-05-05 8:03 ` Harald van Dijk [this message]
2006-05-05 8:33 ` Donnie Berkholz
2006-05-05 8:43 ` [gentoo-dev] " Bart Braem
2006-05-05 11:28 ` Duncan
2006-05-05 8:57 ` [gentoo-dev] " Patrick Lauer
2006-05-05 9:44 ` Diego 'Flameeyes' Pettenò
2006-05-06 6:48 ` Philip Webb
2006-05-06 11:41 ` Diego 'Flameeyes' Pettenò
2006-05-06 12:48 ` Philip Webb
2006-05-06 13:01 ` Jakub Moc
2006-05-06 13:18 ` [gentoo-dev] " Duncan
2006-05-05 10:50 ` [gentoo-dev] " Caleb Tennis
2006-05-05 11:27 ` [gentoo-dev] " Bart Braem
2006-05-05 11:19 ` [gentoo-dev] " Carsten Lohrke
2006-05-05 11:50 ` [gentoo-dev] " Bart Braem
2006-05-06 9:28 ` [gentoo-dev] " Richard Fish
2006-05-05 7:37 ` [gentoo-dev] " Philip Webb
2006-05-05 11:00 ` [gentoo-dev] " Duncan
2006-05-05 21:52 ` [gentoo-dev] " Jan Kundrát
2006-05-05 12:03 ` Marius Mauch
2006-05-04 13:05 ` Duncan
2006-05-04 13:47 ` Guillaume Pujol
2006-05-06 8:56 ` Richard Fish
2006-04-04 11:50 ` [gentoo-dev] " Carsten Lohrke
2006-04-08 13:41 ` Wernfried Haas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060505080354.GA13723@gentoo.org \
--to=truedfx@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox