Mailinglist Archive: opensuse (3605 mails)

< Previous Next >
Re: [opensuse] SuSE-watcher/ksmarttray
  • From: Pascal Bleser <pascal.bleser@xxxxxxxxx>
  • Date: Sat, 03 Jun 2006 15:25:10 +0200
  • Message-id: <44818DB6.4010506@xxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Harry ten Berge wrote:
> Pascal Bleser wrote:
>> Michael Schueller wrote:
>>>> Am Samstag, 3. Juni 2006 01:31 schrieb Pascal Bleser:
>>>>> It's very simple though, it just calls "smart update" on a
>>>>> regular basis (interval is hardcoded in the sources), checks the
>>>>> output and reports it. So it's a lot like SuSE-watcher.
>>>>>
>>>>> If someone with some KDE hacking skills would like to spend a
>>>>> little time on it, I think it's pretty easy to expand (it already
>>>>> does the dirty job of interfacing with smart)... or even use
>>>>> SuSE-watcher and copy/paste the ksmarttray code "smart update"
>>>>> output checking code into it.
>>>> if anybody would patch the suse-watcher to check about new updates
>>>> with the smart engine, it would check the smart sources
>>>> (channels=sources > jpp) for updates.
>>>> If you then press the Button "Update now", the SuSE(Yast) Online
>>>> Update would appear, which has mostly different sources.
>>>> So it would only make sence when the hacked suse-watcher only checks
>>>> the suse update repo, and for all other sources you can use
>>>> ksmarttray...
>>
>> Well, obviously suse-watcher should also be modified to start "smart
>> --gui" instead of YOU (but that's really the easy part) ;)
>>
> I would really *love* that!
>
> Since thursday I'm a new Smart lover,

*g* yet another lover, smart sure is a busy h...er ;)))

> And the main reason I like it so much (besides the fact that it actually
> works perfectly ;-) is that it provides a distribution-independant solution.
> I think that this is good for general acceptance of Linux on the
> desktop.
> No need to re-invent the wheel everytime...

Absolutely, from that point of view, smart has a huge potential.
While it will most probably never become the "default" package manager
on all distributions, it is nevertheless available for all
distributions, and you can use it everywhere.
Same tool, same commands, and the same frontends.

Actually, one could write a more capable GUI for package management,
based on smart, which would work on any distribution.

Personally, I'm rather focusing on smart on SUSE Linux, but the
potential is there ;)

> What I would like to see that the SUSE specific channels you added to
> the package (thank you for that!) will be done in a separate package.
> So the distribution comes with a default package with the Smart
> tooling, and a separate package with all known additional distribution
> specific repositories.

- From a technical point of view, I would tend to agree.
But not for the sake of end-users, at least for the less experienced.

Installing smart on 10.1 currently already is pretty much jumping into
hoops for beginners (especially when zypp doesn't work :\), mostly for
installing python-rpm first (smart depends on it, and it's not installed
by default). Then they have to install smart. Having to install another
package (e.g. "smart-suse") will make the procedure even longer (and
possibly more complex):
http://spinink.net/2006/05/20/installing-smart-package-manager/
http://dev-loki.blogspot.com/2006/05/how-to-install-and-use-smart-on-suse.html
http://www.desktoplinux.com/articles/AT3456783210.html

Another option would be to write some good bash script that would handle
all the nitty-gritty, and less experienced users would just need to run
that.
wget http://......./smart-install-suse.sh
bash ./smart-install-suse.sh

It would check for rpm-python, install it if it's not present, grab the
latest smart RPM, and then the latest smart-suse RPM.

Having to run a shell-script that you grab from the internet as root is
certainly not the most secure way of doing things, but in the end,
people have to trust those who build the packages anyway (but at least
packages have signatures and checksums).

Apart from that, I would have to split out another subpackage for things
that were previously contained in the "main" package.
That's going to be an issue for people who already have smart installed
and upgrade to that version.

I'm not sure I like it.

> But first we need a KDE Smart gui :-)

Well, yeah, possibly. Though that's not really high priority IMO.
A good GUI, whatever the toolkit is, be it GTK2 or QT/KDE.
Even though I use KDE as my desktop environment, I don't really care if
the GUI uses GTK2, as long as its good.
But I always use "smart --shell" so I won't care about that in the first
place ;)

cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\ <pascal.bleser@xxxxxxxxx> <guru@xxxxxxxxxxx>
_\_v The more things change, the more they stay insane.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFEgY22r3NMWliFcXcRAtjoAJsExenzJqPh1mxBaKc8oMmekeIgHQCgsT1Q
5LGBxwcB2HB4cla+/Pf/8Wo=
=FW4k
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-help@xxxxxxxxxxxx

< Previous Next >