[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re:  A proposal to deal with the current RedHat situation
From:       "Roberto H. Alsina" <ralsina () kde ! org>
Date:       2002-09-02 16:41:30
[Download RAW message or body]

On Mon, Sep 02 2002 at 06:37:03pm +0200, Rob Kaper wrote:
> On Monday 02 September 2002 18:16, Shawn Gordon wrote:
> > they are some scripts that we made to automate the process, no we are not
> > giving the scripts away, but that is hardly relevant to building the
> > software, it's not sticking something into the binaries or anything.  we
> > might productize the process, or we might decide to give it away at some
> > point, we haven't made a decision on it yet, so we are just keeping it to
> > ourselves for the moment.
> 
> I'd be against the use of proprietary tools to develop and distribute KDE. 

Thi is just the use of a proprietary tool to call the free compiler,
it adds no proprietary code to KDE, it is only used for building binaries,
not for developing, and the binaries it produces can even be rebuilt 
without it (I am guessing it also produces srpms).

It is even less controversial than using bitkeeper in the kernel.

> Sure, it won't affect the sources. But if users start to rely on the service 
> and we have to shut it down because of any proprietary components we'd create 
> a lot of bad karma.

Importance of risk of not creating binaries << Importance of certainty of not creating binaries.

 ("\''/").__..-''"`-. .         Roberto Alsina
 `9_ 9  )   `-. (    ).`-._.`)  ralsina@kde.org
 (_Y_.)' ._   ) `._`.  " -.-'   Former KDE Developer (MFCH)
  _..`-'_..-_/ /-'_.'           
(l)-'' ((i).' ((!.'             Buenos Aires - Argentina
"You can't be an emperor because some moistened 
bint lobbed a scimitar at you!" Monty Python.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]