To view parent comment, click here.
To read all comments associated with this story, please click here.
You got caught out on your lack of knowledge on Gentoo basic release system which is Mask;unstable;stable. First by insisting that the later releases of the KDE3 branch were not available. To cover up this you moved onto implying that a *new* release should *automatically* be marked stable on an ecosystem of 1000's of packages, without proper testing even though as a user you have the possibility of overriding this if *you* think you know better than the developers. I even pointed out possible exceptions to this. Finally you moved onto the fact that KDE4 should be available for Gentoo, after it being pointed out that you could simply use a SVN build for an unreleased *Major* component involving large numbers of users most of whom rely on having a *working* OS hense all the Masking; Unstable; Stable stuff; You have finally Moved onto saying that a yet unreleased package should be part of the main system. I will point out that its not unusual for releases of this Magnitude to have pre-releases available as masked packages, but like I say having official packages of unreleased components is crackers. Your defending your own lack of knowledge. You have wasted this thread by not researching how Gentoo works.
Your final comment is suitably bizarre..and new and I will respond to it. Innovation...I love this word plenty on here use it but its become crass, and real innovation like sugar is ignored.
You are arguing that Gentoo should *not* use Vanilla packages, on a Meta-Distribution. If you so not see the irony of that statement than I give up. Gentoo allows you to use whatever alternative menu you want in KDE...or any desktop allows you to swap and change components however you want. The KDE-Lite package allows you to install the components of KDE you want and no others. Any new component would just become *another* package. Although personally I'm against anything that is is not Vanilla unless its a real fork.
Now the reality is that Gentoo *specific* packages exist...the *sensible* ones. Installers and portage GUI for easier installation and management, and components that add a Gentoo look.
If you are saying that Gentoo does not add bugfixes, or have developers that both work on packages, clearly you have never used Gentoo. In a lot of ebuilds portage sub-directory there is a directory marked files which contain various patches. Which are submitted back to the developers...and the source is available to everyone the code is distributed to.
The bottom line is your a timewaster.
Edited 2007-07-24 23:42
first i never moved from a statement to another.
all i have already said are valid.
You must be new in gentoo so it's ok by me.
Please consider that i'm not asking for something new
if i remember right they had ebuilds for all alpha,beta,rc releases with patches in portage in old days (missed them ;_;) for kde.
if i also recall right gentoo had also many ebuilds for prerelease of gnome for version 2 (a major release).
so it's not something new because that time everyone was living at real bleeding edge.
and... no... contribution is in a low lvl.
Most of the times the patches they use are coming from upstream.
For example, recently they removed xine support from totem (they said none from the team use xine lol). Of course it's easy for me to make a new ebuild but..hey.. is that the freedom u ask for?
What if we have to do with a more complicated installation?
Another example...
There is a well known bug in wxgtk that crashes applications like amule (both stable).
It exists for MONTHS and you know it's not an easy case. You cannot always make the superman and fix ebuilds or update them your own.
Bugs depends on other bugs and a user can't make it all by himself.
I think the msg is simple and well known to the management...
Gentoo has to make serious recruits and be more policed, with new ideas and freedom for their developers to make as they wish and have FUN.







Member since:
2006-06-09
my friend you are confusing an official maintained kde4 ebuild i'm asking for (with local revisions, patches at least to compile in gentoo, accept bugs in bugzilla, developers focused in nothing else than the particular project etc etc) with a dirty ebuild which just downloads the latest dev code and builds it...
well you think i'm confused and i think you are confused too. call it a draw? :p
anyway feel free to read a part of social contract:
"We will establish relationships with Free Software authors and collaborate with them when possible. We will submit bug-fixes, improvements, user requests, etc. to the "upstream" authors of software included in our system. We will also clearly document our contributions to Gentoo as well as any improvements or changes we make to external sources used by Gentoo (whether in the form of patches, "sed tweaks" or some other form). We acknowledge that our improvements and changes are much more meaningful to the larger Free Software community if they are clearly documented and explained, since not everyone has the time or ability to understand the literal changes contained in the patches or tweaks themselves."
http://www.gentoo.org/main/en/contract.xml
and tell me now in which way gentoo project contributes e.g in kde?
how many developers are working on kde4?
and not just kde but any other project...
let me remind you that most major "static" distros contribute with innovative code, one guy from suse made a new kde menu, the other guy from ubuntu made a new menu editor for gnome etc etc...