Freitag, 30 Jan 2009

Howdy

KDE 4.2 is more or less ready for testing, but we have
some open tasks before we will officially call for testing.
We would like to know how many people are still using
KDE4 on FreeBSD 6.4? We are considering dropping
support for 6.x.

Let me explain.

First of all it is sad to say, but currently there are
only 2 people who actively work on KDE4. It is _really_
hard work to get KDE4 ready for FreeBSD. Also it is
getting harder to build KDE4 with gcc 3.x. Of couse
if somebody want to support KDE4 on 6.x you are
welcome to our team! Try to compile KDE, make
patches and push them upstream! So, in order to
move forward we may have to drop 6.x support.
We just don't have the manpower to build multiple
versions.

A few private words to the FreeBSD KDE users.

A lot of you want to have the latest KDE4 in the ports tree,
but we haven't had much success getting people to help.
Last year when we called for help, not many responded.
If you want us to release new versions in a timely
manner, please pitch in and help.

Ok, enough for the moment. What do you think about
6.4 support?

16 Responses to “”

  1. Uwe Grohnwaldt Says:

    I think the Support for FreeBSD 6.4 should be dropped. All people I know don’t use this as a desktopsystem (with KDE). Most use RELENG_7 or HEAD.

  2. Daniel Seuffert Says:

    Support for FreeBSD 6.4 should be dropped. KDE is for desktop users only and most of them use the latest release (7.1 now) version anyway. If somebody wants to stay with 6.4 she/he can use KDE 3.5.10 anyway.

    You cannot support unlimited demands with limited resources. Please concentrate on support for 7.x!

    Thank you for all the hard work!

    Best regards, Daniel

  3. Andreas Nilsson Says:

    I suggest dropping 6.x.

  4. Artis Says:

    I’m in complete agreement with Daniel here.

  5. Prudhvi Krishna Surapaneni Says:

    Yeah,

    I agree we should drop support for 6.x

  6. GregK Says:

    Agree that you should drop anything older than the lastest STABLE for the latest in KDE.

  7. Gustau Pérez Says:

    If homepower is limited, support for 6.X should be dropped. The reason is that the main FreeBSD site states that 6.4 is legacy. So support should be granted for production series, and if possible and feasible, grant support for legacy.

  8. kein KDE 4.x für FreeBSD 6.x » F!XMBR Says:

    [...] want us to release new versions in a timely manner, please pitch in and help. So miwi auf seinem Blog. Und dem ist auch nicht viel hinzuzufügen, zwei Maintainer reißen sich auf gut Deutsch den Arsch [...]

  9. wen Says:

    I’m in agreement dropping support for 6.4.

  10. Aron Schlesinger Says:

    I’m in complete agreement too with Daniel here.

  11. Chris Ruiz Says:

    AFAIK 6.x is basically EOL and there will be no future releases, so it doesn’t make sense to go out of your way to support it.

  12. Status report KDE 4.2 and FreeBSD 6.4 support | FreeBSD - the unknown Giant Says:

    [...] 4.2 and FreeBSD 6.4 support Saturday, February 7th, 2009 | FreeBSD | Gerard Martin Wilke announced that KDE 4.2 (FreeBSD) is ready for testing. He’s also interested to find out how many users [...]

  13. MK Says:

    Ouch. Heckuva way to find out. I didn’t see a comment in /usr/ports/UPDATING. Maybe I missed it, though I try to read it as carefully as I can. Maybe the latest port revisions shouldn’t be in the ports tree for 6.4 if they don’t build.

    Will KDE42 build & run using akonadi-1.0.0_1, phonon-4.2.0_1 ?

    Not all of us have have a fixation/fetish about compiling the latest sources the moment they’re released. :-)

  14. arturbac Says:

    What about the gcc4 port on 6.4 ?

    Let me explain:
    6.x is the latest stable working release of FreeBSD on many desktops.
    7.x in my opinion is still only an alpha buggy release.

    After year of reporting bugs in filesystem on SATA Nvidia nforce platform there is still imposible to use 7,x branch with amd64 with that chip, 6,x is working fine …

  15. DimanNe Says:

    6.4 support must be dropped

  16. pastor Says:

    shit … :(

Leave a Reply

»
«