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

List:       kde-core-devel
Subject:    Re: kioslave location
From:       David Faure <faure () kde ! org>
Date:       1999-11-11 18:31:30
[Download RAW message or body]

On Thu, Nov 11, 1999 at 09:48:22AM -0700, Kurt Granroth wrote:
> David Faure wrote:
> > I didn't want to post anything on this subject anymore, but your
> > remarks leave me no choice.
> 
> I'm hesitent to post more, too... but like you, I'm left with no
> choice :-/
> 
> [huge snip]
> > Anyway we agree, an app should "work", more or less, without kdebase
> > installed.  If the pop3 ioslave is moved to kdenetwork, the only app
> > that wouldn't have worked (in the sense of basic functionality)
> > would have been kmail and that's why I said "the issue is closed".
> [and snip]
> > Wrong. Tell me which app doesn't app if the kioslaves (besides
> > kio_file of course) are not installed ?  The (future) kmail issue
> > has been solved, and for any other KDE app using libkio, they can
> > skip kdebase if they are, for instance, not connected to the net.  I
> > don't need kio_ftp and kio_http if my host isn't connected to the
> > net, and still apps work FINE !
> 
> > If one wants an internet-enabled KDE, one should install kdebase.
> > That's what I called : skip it if you want but if you want FULL
> > functionality you have to install it. I don't see any inconsistency
> > here.
> 
> David, you are limiting your thinking here!  Remember that we are
> pushing KDE as a development platform as well as a desktop
> environment.  We want developers to code their applications in KDE.
> Our biggest selling point is all of the inherent functionality --
> including network transparency!
And you're limiting your thinking because you forget about
all the other things in kdebase that are required.
Once more, something to read help pages, something to configure
the app....

> This doesn't just apply to current apps in our core packages!!  We
> want *all* apps ported to or written for KDE -- not just the few in
> kdeutils, kdenetwork, kdegraphics, etc.
> 
> So say I'm a 3rd party developer and I have an app that wants to use
> the ioslaves for SMB or tar or LDAP access (assuming that they
> worked).  My app is maybe 200K but is very useful and lots of people
> would like to use it.  However, right now, I would have to *require*
> that all of my users install all of kdebase -- all umpteen megabytes
> of it.
kdebase is too big, we all agree. But that's a different issue.

> Say this app I'm developing is the worlds best mail client.  Now you
> are saying that I must require my users to install kdenetwork.  Why
> should they have to do that?

Since your app is a KDE app, users will need khelpcenter to read its help,
kcontrol to configure it, ... Which is where kdebase makes sense
more than putting kio_pop in kdenetwork. Hmmm...

> *sigh*
> 
> All of the non-technical issues are a pain.  We have the philosophy
> that code matters more then words.. but in a case like this, there is
> no code -- it's all words.  And the philosophy that whoever suggests
> something should do it doesn't apply either since we are talking about
> a shared resource.
That's right.

> I think I'm going to shut-up on these issues and just put out my own
> packaging sometime soon (maybe around KRASH) time.  It would have
> identical source to the official KDE packages but would be arranged in
> a different way.  No silly arguments and no endless decision making
> process...

-- 
David FAURE
david@mandrakesoft.com, faure@kde.org
http://home.clara.net/faure/
KDE, Making The Future of Computing Available Today

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