public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rainer Groesslinger" <rainer.groesslinger@gmx.net>
To: <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Gentoo "stable" going in wrong direction ?
Date: Sun, 15 Dec 2002 13:56:05 +0100	[thread overview]
Message-ID: <DDEPKFNMNPHHLGFONDKMCEGJCBAA.rainer.groesslinger@gmx.net> (raw)

Hello,

I have been looking around for sime time in various ebuilds since Gentoo
introduced the "stable" and "testing/unstable" feature...

Well, in general I think it is a very good idea but I don't think it is used
as it should be !

For example Maik "blizzy" Schreiber told me about
http://gentoo-stable.iq-computing.de which is something like a "voting
system" but almost nobody is using it (for example mozilla 1.2.1 only has
one vote although many thousand people are using it - with success) and if
you take a look at the ebuild you see that every mozilla ebuild with version
1.2.1 has the keyword ~x86 - so stable users don't get it although there's
no reason for calling Mozilla 1.2.1 "unstable"...

In my opinion http://gentoo-stable.iq-computing.de should be a more-or-less
official voting system for the packages or gentoo stable will end like
debian stable and I don't think Gentoo wants to go *that* stable :)

There are just not enough users and feedback pushing unstable packages to
stable from what I see...

There was/is talk about package.mask being removed in the future - good idea
but I think it should look like this

stable: KDE 3.0.5
unstable: KDE3.1RC5

stable: Mozilla 1.2.1
unstable: Mozilla 1.3a

and so on...In short: Gentoo stable should be as close as possible to what
the developers of the various applications call "stable" - why not believe
them ? ;p

Currently the package.mask carries packages which have a right to be called
unstable, e.g. XFree 4.2.99 and so on...
But the stable/unstable situation in some ebuilds is a bit confusing and
leading in the wrong direction if continued like this ?

Of course every distribution needs to test individual things, make some
changes here and there...And to avoid a bad stable tree I highly suggesst
using blizzy's system...

I didn't know of it, he just told me some minutes ago and I think it's a
great chance for people to vote for it etc. - if it's used and developers
set their ebuilds as 'stable' according to what people voted (or not)...


Just my opinion about current stable/unstable things...
Rainer



--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2002-12-15 12:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-15 12:56 Rainer Groesslinger [this message]
2002-12-15 18:43 ` [gentoo-dev] Gentoo "stable" going in wrong direction ? Saverio Vigni
2002-12-15 18:03   ` Maik Schreiber
2002-12-16 18:30 ` foser
2002-12-16 20:34   ` Maik Schreiber
2002-12-16 20:38     ` Jon Portnoy
2002-12-16 20:43       ` Maik Schreiber
2002-12-16 20:46       ` [gentoo-dev] Gentoo &quot;stable&quot; " Matthew Walker
2002-12-16 20:50         ` Maik Schreiber
2002-12-16 20:50     ` [gentoo-dev] Re: [gentoo-core] Re: [gentoo-dev] Gentoo "stable" " Martin Schlemmer
2002-12-16 21:04       ` Maik Schreiber
2002-12-16 21:05         ` Martin Schlemmer
2002-12-17  1:05     ` foser
2002-12-17  0:26       ` [gentoo-dev] Re: [gentoo-core] Re: [gentoo-dev] Gentoo &quot;stable&quot; " Matthew Walker
2002-12-17  1:47         ` foser
2002-12-17  0:56           ` [gentoo-dev] Re: [gentoo-core] Re: [gentoo-dev] Gentoo &amp;quot;stable&amp;quot; " Matthew Walker
2002-12-17 10:25       ` [gentoo-dev] Re: [gentoo-core] Re: [gentoo-dev] Gentoo "stable" " Maik Schreiber
2002-12-17 14:12         ` foser
  -- strict thread matches above, loose matches on Subject: below --
2002-12-15 14:07 Pieter Van den Abeele
2002-12-15 14:24 ` Maik Schreiber
     [not found] <DDEPKFNMNPHHLGFONDKMKEGLCBAA.rainer.groesslinger@gmx.net>
2002-12-15 14:34 ` Pieter Van den Abeele

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=DDEPKFNMNPHHLGFONDKMCEGJCBAA.rainer.groesslinger@gmx.net \
    --to=rainer.groesslinger@gmx.net \
    --cc=gentoo-dev@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