Re: [gentoo-dev] ebuilds for kde3 beta etc.

[Guido Bakker <guidob@gentoo.org>]

That's why kde should install in its own directory... It's too big, just like 
X11R6...

--
Guido

sön 2001-12-23 klockan 15.07 skrev Dan Armak:
> On Sunday 23 December 2001 15:44, you wrote:
> > That is why I'm against putting untested early-beta software in the
> > packagesystem. Because no matter how much unsupported they are, we

will

> > always end up support it.
>
> Well, I don't think kde could break anything but kde apps. And I'm

willing to

> support the beta ebuilds.

I wasn't talking about just KDE, but if we put KDE in I can't see why we
couldn't put all alpha-releases. And others might break things. So can
KDE3 if it installs over other files (like pilot-link installing over
glibc and stuff).

And what I'm talking about here is not that the actual code is beta
(since very much of what is in portage now is "beta"). I'm talking about
beta-releases (which are only meant for developers of KDE/GNOME/foo,
depending on what kind of packages it is).

> Of course I'd put up a 'don't use unless you know what you're doing'

notice,

> and mask them thoroughly. And support would be probably slower/more

sparse,

> but not necessarily so since I'll probably be using kde3 myself all

the time

> before long, and I know some other people will do so too before the

final

> release.

Yes probably, and that is what frightens me.

> As for problems that are rooted in kde3 as such (not just beta

trouble), the

> more input and testers the better - as long as they understand that

it's not

> *supposed* to be stable. As I've said, better solve these now than

when

> kde3-final comes out.

Problems that come out of your ebuilds, yes, but really, if the tarballs
used had been tested before being made available in Portage the job of
finding errors in the ebuilds would be less.

Regards,
  Mikael Hallendal