On Monday 28 January 2002 20:58, Whit Blauvelt wrote: > On Tue, Jan 29, 2002 at 12:17:19PM +1100, Ben Burton wrote: > > I'd absolutely advise using all of the sid KDE packages, even if you're > > on a woody system - this is just based on watching bug reports come in > > from people using straight woody or using some woody KDE packages with > > some sid KDE packages. But then again, I'm not sure how many other sid > > packages will be dragged in by asking for sid's KDE. This advice should > > also be taken with a grain of salt because I haven't tested woody at all > > myself. > > Does someone know from experience how well this would work? The most > straightforward way to accomplish it? > > Or is it so messy that the sane thing to do - for someone who wants a > rock-stable OS but at the same time wants to play with bleeding edge > applications - is forget the package approach and compile? > > Whit
My experience has been that using the basic KDE from sid has been rock solid, save for two situations: the libpng mess and a problem with KMail and K6-2 processors that was quickly resolved. On an otherwise woody system, it has installed nothing but the kde apps/libs. Packages that are essentially frontends for other services (such as kdessh) do tend to pull in the related packages though. bob bob
