kde.debian.net needs updating (With this info? And more?)(+ Requests)
Who is in charge of that page?
There are several things that I think should be there. At least the
following points should have info there. Something like the following.
Request 1:
Is there someone who will put the following up there?
**************************************************************************
**************************************************************************
If you want to use the current (2.2) KDE on Debian, you need to run Woody
or Sid.
As of 020129, if you run Woody, you will need to start with the kde-base
package, and add stuff yourself from there.
apt-get install kde-base
See:
http://packages.debian.org/testing/x11/kdebase.html
Ao 020129, if you run Sid, you should start with the kde metapackage.
It includes kde-base, plus many other packages.
apt-get install kde
See:
http://packages.debian.org/unstable/x11/kde.html
http://packages.debian.org/unstable/x11/kdebase.html
**************************************************************************
Ao 020129, for the package kde to move from Sid to Woody (FSTW), the
following things must happen: (Fill in the correct info here: I'm just
trying to show a possible format here, & the below data is just a guess at
what an entry might look like)
Need Depends on Expected to occur approx:
---- ---------- -------------------------
1) m68k is holding up kdebase PPC build group Hopefully 1-2 days
(Hopefully not 1 month)
2) ___
===================================================
===================================================
[***** Personal Request/Suggestion/Encouragement 2: ChrisC: I think it is
_really_ important to get the kde package into Woody. I strongly
encourage you to make that a top priority, if at all possible. I suspect
it is _much_ easier to get a full/useful/complete KDE system set up using
the KDE metapackage (kde) than using kde-base & doing the rest by hand.
[It will also make it much easier, I hope, to write a KDE-Debian HowTo.
:) ]
Specifically, would you provide a short explanation (in
a reply to this email) about exactly what needs to be done to get it there
and what others need to do (ex: the m68k group?).
And: ***** How long do you think that realistically will take? *****
Then perhaps list members could provide some gentle encouragement and
support to the appropriate parties so that this could be done soon? Or,
perhaps as I suggested in
"Consider: Move pkgs from Sid to Woody sometimes for progress (was:Re:."
http://lists.debian.org/debian-kde/2002/debian-kde-200201/msg00651.html
maybe if other parties are delaying the package
movement FSTW, the package could be moved there "ahead of normal
schedule" to better serve the needs of the majority of the community.]
===================================================
[Brief pre-reply to, perhaps, Kamil Kisiel (who pointed out that such
things have been debated before, and regarding which I am interested in
doing, but currently lack time to read the historical debates) and others
wishing to support the principle of:
"The point of Woody is to help
prepare for the next stable release of Debian. Moving in more recent
packages that have bugs in them to replace outdated packages that don't
is a step in the wrong direction. Just because a package is outdated by
several months does not mean it should be replaced by a new buggy
version."
I acknowledge that point,
and do not wish to move bugs into Woody,
but wish it be considered that in point of fact,
given the long time of the Woody release, and nonexistence of current
(2.2) KDE packages for Potato, the currently unreleased Woody has now
defacto _become_ the used/("Stable") release of Debian for making
productive current use of the current release of KDE, and thus it might be
wise to accomodate Debian procedure and principle to the pragmatic reality
of the situation, and perhaps take the supranormal action of getting the
kde metapackage FSTW without meeting all the "normal" requirements for so
doing.
Ah, well, maybe an alternative is to avoid mucking with established
procedures, and just suggest K-D installers use pinning as described in
Pinning Unstable: Woody use of Evolution
http://www.debian.org/News/weekly/2002/1/mail#1
Mixing Debian releases the easy way
http://www.debian.org/News/weekly/2002/4/mail#1
I guess the best case is if it in fact is a very short time till the
standard requirements are met for kde metapackage to go FSTW. ]
===================================================
===================================================
**************************************************************************
Ao 020129, the KOffice package in Woody is about 6 months old (very old).
A new package is actively being worked on by
"Ben Burton" <benb@acm.org>.
"The Sid version of koffice is almost always fairly up to date.
At the moment all that's
keeping koffice out of woody is an arm rebuild and two more days' wait, and
unless some major bug is discovered I'm not going to do another upload until
1.1.1 has progressed into woody. So cross your fingers and koffice for woody
might be up to date in the order of days."
Ao 020129, for the package koffice to move FSTW, the
following things must happen:
Need Depends on Expected to occur approx:
---- ---------- -------------------------
1) nothing few more days& no bugs few more days
**************************************************************************
**************************************************************************
KDE 2.2 for Woody & Sid is maintained by:
"Chris Cheney" <ccheney@cheney.cx>
On 020129 CC said:
I have been a Debian user since around Aug 1998, and have been a
maintainer since July 2000 (I was stuck in the closed NM queue for a
while). I currently have 19 source packages, 18 of which are not KDE
related. Once I upload the all of the KDE packages I think I will have
around 42. I decided to maintain the KDE packages because I use it
every day and didn't want to see the packages deteriorate.
> A) What is the plan/roadmap/future for KDE related things in Debian?
> the metapackage (or, what is it called now? Task?) of kde vs of kdebase.
My plan is to examine all of KDE 2.2.2, which I am currently doing. Then
I will upload a final set of packages so that they can make it into
Woody. Then I will start preparing KDE 3 debs and will host them on
p.d.o/~ccheney/ until KDE 3 is released or Woody is frozen whichever
happens first.
> C) What's your recommendation regarding: would you advise people who want
> to be making productive use of KDE now to run Woody or Sid?
Well I thought that fixed KDE 2.2.2 would be in woody by now but it
appears that m68k is holding up kdebase for a build deps (seems odd). I
will try to get it in as soon as possible though. Sid should be fine if
you want to run that.
currently you probably still need to run Sid, but hopefully this
situation will change soon.
sid has the KDE meta packages which I don't think are in woody yet? The
meta packages make it much easier to install KDE.
> D) What's up w/ KDE 3?
KDE 3 is still a bit buggy from what I hear, I haven't actually built
debs for it yet since I am still working on the 2.2.2. I would imagine
that I will have good working debs by the time it is officially released
(hopefully sooner). KDE2 and KDE3 can not be installed at the same time
without some work, and I will not be supporting both of them being
installed at the same time. I am not going to have both in the archive
at the same time since it would take an enormous amount of space, if I
remember correctly someone said KDE currently takes approximately 2.5GB
of archive space now (between all the archs and woody/sid).
**************************************************************************
**************************************************************************
__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions!
http://auctions.yahoo.com
Reply to: