[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-usability
Subject: Re: KSystemUpdate
From: Kari Pihkala <kari.pihkala () gmail ! com>
Date: 2005-11-15 16:18:09
Message-ID: 4d756b2a0511150818n27389915re54accd98f5e38d7 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Check out this article about Ubuntu update-notifier for Gnome. It sounds
similar to your idea.
A similar application is planned for Kubuntu (KDE version).
http://gnomejournal.org/article/19/simplified-package-management-in-ubuntu-=
hoary
Cheers,
Kari
On 11/11/05, Johan De Messemaeker <johan.demessemaeker@telenet.be> wrote:
>
> On Friday 11 November 2005 14:31, Zak Jensen wrote:
> > I would suggest investigating other avenues of retrieving updates
> > before adding yet another "package management" system to the world of
> > linux/bsd. I believe the best place to start would be with the
> > Autopackage team, but you may also want to talk with the devs for
> > YaST, Yum, and Apt. Another place one could branch from is
> > KGetNewStuff.
>
> The application is just a frontend to ensure a consistent interface over
> different package management systems (BSD ports, emerge, apt-get, RPM and
> soon windows). Nothing more. I'm not interested in reinventing the wheel
> here :)
>
> There are already a zillion different frontends available for almost ever=
y
> package technology. This is not helpful to beginning users.
>
> > One concern that I have for your project overall is that users don't
> > generally like it when their computers start doing things on their
> > own... particularly the type who perfer linux, and expecially when it
> > is sending "information" to the Internet. I highly recommend
> > investigating how to make this an optional affair, so that all
> > outbound updating activities could be disabled from 1 common location.
> > (Maybe on an app-by-app basis, but that might make it too
> > complicated.)
>
> That's _exactly_ why I'm interested in this kind of application.
> KSystemUpdate
> (it's a cheesy name isn't it :P) _won't_ install anything automatically:
> all
> it does is check some servers for various upgrade information and then
> show
> that information in a consistent, clear and easy-to-use manner. From
> there,
> users can upgrade the parts they like.
>
> Additional (advanced ?) options are possible ofcourse: it would be nice t=
o
> be
> able to eg schedule stuff (eg: upgrade these applications within 3 hours)=
.
>
> Regards, Johan
>
> PS: that's quite the example you mentioned: YaST. Since KDE is getting a
> major
> rewrite for KDE 4.0, and so is KControl, wouldn't it be beneficial for th=
e
> KDE project to have a YaST like program ? Since KDE is already
> cross-platform
> (and soon available on another major platform) it would be great to have
> an
> build-in KDE abstraction over OS/server/client configuration. That should
> be
> a feature for a cross-platform desktop IMO.
> _______________________________________________
> kde-usability mailing list
> kde-usability@kde.org
> https://mail.kde.org/mailman/listinfo/kde-usability
>
[Attachment #5 (text/html)]
<div>Check out this article about Ubuntu update-notifier for Gnome. It sounds similar \
to your idea.</div> <div>A similar application is planned for Kubuntu (KDE \
version).</div> <div> </div>
<div><a href="http://gnomejournal.org/article/19/simplified-package-management-in-ubun \
tu-hoary">http://gnomejournal.org/article/19/simplified-package-management-in-ubuntu-hoary</a><br> </div>
<div>Cheers,</div>
<div>Kari<br> </div>
<div><span class="gmail_quote">On 11/11/05, <b class="gmail_sendername">Johan De \
Messemaeker</b> <<a \
href="mailto:johan.demessemaeker@telenet.be">johan.demessemaeker@telenet.be</a>> \
wrote:</span> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px \
0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Friday 11 November 2005 14:31, Zak \
Jensen wrote:<br>> I would suggest investigating other avenues of retrieving \
updates <br>> before adding yet another "package management" system to \
the world of<br>> linux/bsd. I believe the best place to start would be with \
the<br>> Autopackage team, but you may also want to talk with the devs for \
<br>> YaST, Yum, and Apt. Another place one could branch from is<br>> \
KGetNewStuff.<br><br>The application is just a frontend to ensure a consistent \
interface over<br>different package management systems (BSD ports, emerge, apt-get, \
RPM and <br>soon windows). Nothing more. I'm not interested in reinventing the \
wheel<br>here :)<br><br>There are already a zillion different frontends available for \
almost every<br>package technology. This is not helpful to beginning users. \
<br><br>> One concern that I have for your project overall is that users \
don't<br>> generally like it when their computers start doing things on \
their<br>> own... particularly the type who perfer linux, and expecially when it \
<br>> is sending "information" to the Internet. I highly \
recommend<br>> investigating how to make this an optional affair, so that \
all<br>> outbound updating activities could be disabled from 1 common location. \
<br>> (Maybe on an app-by-app basis, but that might make it too<br>> \
complicated.)<br><br>That's _exactly_ why I'm interested in this kind of application. \
KSystemUpdate<br>(it's a cheesy name isn't it :P) _won't_ install anything \
automatically: all <br>it does is check some servers for various upgrade information \
and then show<br>that information in a consistent, clear and easy-to-use manner. From \
there,<br>users can upgrade the parts they like.<br><br>Additional (advanced ?) \
options are possible ofcourse: it would be nice to be <br>able to eg schedule stuff \
(eg: upgrade these applications within 3 hours).<br><br>Regards, Johan<br><br>PS: \
that's quite the example you mentioned: YaST. Since KDE is getting a major<br>rewrite \
for KDE 4.0, and so is KControl, wouldn't it be beneficial for the <br>KDE project to \
have a YaST like program ? Since KDE is already cross-platform<br>(and soon available \
on another major platform) it would be great to have an<br>build-in KDE abstraction \
over OS/server/client configuration. That should be <br>a feature for a \
cross-platform desktop \
IMO.<br>_______________________________________________<br>kde-usability mailing \
list<br><a href="mailto:kde-usability@kde.org">kde-usability@kde.org</a><br><a \
href="https://mail.kde.org/mailman/listinfo/kde-usability"> \
https://mail.kde.org/mailman/listinfo/kde-usability</a><br></blockquote></div><br>
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic