On Tue, May 21, 2002 at 06:06:42PM +0200, Guy.Bormann wrote:
> 
> So what?!! _AGAIN_, Mandrake Cooker is _not_ supposed to be used for
> real world usage!
> How hard is this to understand? Jeezzz, why do
> people keep complaining about this?

Fuck off!  I have been here working with Cooker a hell of a lot longer
than you have and know exactly what Cooker is for and what it's not
for!  I don't need the likes of you talking down to me thank you very
much.

Now go and re-read my message, I said "real-world" usage, not mission
critical and not even "work-place" usage.  Yes, even casual, testing
use has to interact with the real-world or what kind of testing would
it be without real-world use?

> See, above : The raison d'etre of Cooker is exactly that, namely to get an
> up to date distribution and resolving all the dependency/interoperability
> issues that comes with upgrading.

Uhm, like a non-working Java perhaps.  You seem to miss the point that
making Java work with Cooker/next release of Mandrake Linux is not
something that is under Mandrake's control.  The java package is
released as pre-compiled binaries and if it don't work with Mandrake
Linux it will be Mandrake's problem to resolve, not Sun's.  THIS IS MY
POINT DICKHEAD!

> If you want to use Cooker
> "in real world usage" you are completely on your own and no guarantees are
> given (and _none_ should be given) that it won't break in the meantime
> towards full release.

Oh thanks for your disclaimer.  Now go re-read the difference between
"real-world usage" and mission critical usage.  I am not looking for
any guarantees of usage, just clarifying the position of Mandrake when
it comes time to release a Mozilla that does not work with Java.

> I'm here only a few months just observing the mailing list,

Well then maybe you should shut your mouth instead of opening in and
immediately putting your foot into it.

> Now go read it again!

You really are an asshole aren't you?

b.

-- 
Brian J. Murrell

Attachment: msg64506/pgp00000.pgp
Description: PGP signature

Reply via email to