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

List:       kde-devel
Subject:    Re: starting to write a KDE auto-installer
From:       Larry Wright <larry.tami () gte ! net>
Date:       2001-08-22 0:58:14
[Download RAW message or body]

On Tuesday 21 August 2001 01:11 pm, Waldo Bastian wrote:

<snip>
> The rationale behind this is that KDE focuses on its primary activity:
> producing Desktop software for Unix. FTP-servers, CVS-servers, mailservers
> etc. are there to support this primary activity. Distributing KDE software
> to end-users is not a primary activity of KDE, this is rooted in two facts:
</snip>

Ok, I must be missing something obvious here. If so, feel free to yell at me. 
That said, I don't see why the server capacity is such a big deal, at least 
for the majority of users. All of the major distros provide some sort of 
update facility (I'm speaking of SuSe, Mandrake, and I believe Red Hat). I 
know for a fact that SuSe and Mdk both host these updates on FTP servers. In 
my thinking, all we need for these distros is a statically linked app that 
points to those FTP servers. And for any apt-based distro it's simply an 
apt-get whatever. This takes care of most users, particularly new ones (which 
is really what we're targeting here, right?). New users (those unfamiliiar 
with *nix) are unlikely to install Slackware or one of the BSD's.  What would 
be very helpful here is if the major distros would put some of the more 
obscure dependancies alongside with KDE (SuSe is really guilty here, esp. 
when it comes to KDevelop).

So, am I nuts?
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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