Sulfur vs rigo

[Zenchy]

installing sulfur was the first thing i did...
but was not able to start sulfur

Code: Select all

No protocol specified
/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
  warnings.warn(str(e), _gtk.Warning)
/usr/lib/entropy/sulfur/sulfur/core.py:110: GtkWarning: IA__gdk_cursor_new_for_display: assertion `GDK_IS_DISPLAY (display)' failed
  def busy_cursor(mainwin, insensitive=False, cur = gtk.gdk.Cursor(gtk.gdk.WATCH)):
Traceback (most recent call last):
  File "/usr/lib/entropy/sulfur/sulfur_client.py", line 32, in <module>
    from sulfur import SulfurApplication
  File "/usr/lib/entropy/sulfur/sulfur/__init__.py", line 59, in <module>
    from sulfur.packages import EntropyPackages, Queue
  File "/usr/lib/entropy/sulfur/sulfur/packages.py", line 34, in <module>
    from sulfur.package import EntropyPackage, DummyEntropyPackage
  File "/usr/lib/entropy/sulfur/sulfur/package.py", line 21, in <module>
    from sulfur.entropyapi import Equo
  File "/usr/lib/entropy/sulfur/sulfur/entropyapi.py", line 27, in <module>
    from sulfur.dialogs import LicenseDialog, okDialog, choiceDialog, inputDialog
  File "/usr/lib/entropy/sulfur/sulfur/dialogs.py", line 41, in <module>
    from sulfur.core import UI, busy_cursor, normal_cursor, \
  File "/usr/lib/entropy/sulfur/sulfur/core.py", line 110, in <module>
    def busy_cursor(mainwin, insensitive=False, cur = gtk.gdk.Cursor(gtk.gdk.WATCH)):
RuntimeError: could not create GdkCursor object


[Zenchy]

well rigo is the hughest fail i ever seen. it's totaly unusable and unuseful. Even equo it self is more usable

1. fail able to install only one item
if you want to install a lot of packages without a meta-package u need to click every single one to installing instead of selecting them all and install them together... thats what a gui is for

2. fail leak of a not operator
you can say
in:categaor in:installed
but not
in:categor not:installed
you need to click on every single item to see if its installed or not

3. fail leak of informations displayed
if you search for items you see even lees informations about a package then in a equo search. so you need to click again on more details

4. fail not configurable
its fine for me if people like simple tools without any funktionality, but give users the optinons to configure the tool to there needs.

5. fail replacing sulfur by rigo
Missed the point where Sabayon became Sabuntu -.- let the user desicde what they want to use, not dictate it

[albfneto]

In my oppinion, i like Rigo, i liked Sulfur also and i like entropy. In fact, i like practically all in Sabayon: KDE. MATE, window maker, LXDE, XFCE, E17, Compiz. I dislike only few things, as GNOME3, GNOME-Shell and Cinnamon, they are very unstable and no configurable, I also not like Grub2 so much, i prefer grub legacy, more simple and more practical.

About Rigo and Sulfur, i enjoy Rigo for complete upgrades, but for search many packages that you not know the name (ex. keyword compiz, shows all tthe compiz packages) Sulfur was much easier. Another utility is to control upgrades. For example,one of my sabayons is GNOME2 oriented, using Sulfur i was able to see all the names of upgrades and mask then for not overwrited my GNOME2... Unfortunately,it no more works.

But, you remember the general installer for linux packages? PACKAGEKIT, and their GUIS: Kpackagekit for KDE and gnome-packagekit, for GNOME? They works in Sabayon, see:

https://forum.sabayon.org/viewtopic.php?f=57&t=24753&p=138140&hilit=install+packagekit#p138140

[tekwyzrd]

I strongly dislike Rigo. It's crippled by the "less is more" attitude and belongs with a distribution like Ubuntu that appeals to those who are easily confused by options and reminds me of the original kde4 system settings app based on ubuntu control center. Not what I'd call "bleeding edge".

Sulfur not working after running equo upgrade today. When started in a terminal the result is:

Code: Select all

# sulfur
Traceback (most recent call last):
  File "/usr/lib/entropy/sulfur/sulfur_client.py", line 32, in <module>
    from sulfur import SulfurApplication
  File "/usr/lib/entropy/sulfur/sulfur/__init__.py", line 59, in <module>
    from sulfur.packages import EntropyPackages, Queue
  File "/usr/lib/entropy/sulfur/sulfur/packages.py", line 34, in <module>
    from sulfur.package import EntropyPackage, DummyEntropyPackage
  File "/usr/lib/entropy/sulfur/sulfur/package.py", line 21, in <module>
    from sulfur.entropyapi import Equo
  File "/usr/lib/entropy/sulfur/sulfur/entropyapi.py", line 32, in <module>
    from entropy.const import etpConst, etpUi, const_debug_write
ImportError: cannot import name etpUi

Before someone suggests it I re-installed using entropy and portage with the same results. Standard repository, not limbo.

[sabayonino]

Don't run sulfur as root

Use "sudo" or "gksu" or "kdesu"

[batvink]

No need for, Sabayonino.
Just run Sulfur as normal user, and it automatically should ask for the root password.

tekwyzrd,
Please read the wiki., Sulfur is replaced by Rigo.
Allthough still available in the Repositories, it is no longer developed and will most likely NOT work anymore.

[ElectricPrism]

I was just as confused about the Sulfur / Rigo question as the wiki is still in need of being updated to the latest info.

I actually find that Rigo is somewhat buggy but also sufficient. After 2 days of tailoring Sabayon KDE I much prefer using the package website over the built in Rigo:
https://packages.sabayon.org/

It'd be really cool if Sabayon hooked into the local system using a kind of magnet link from the browser suchas: SSP://92322
Which would corrolate to the "92322 = App ID" package and launch the Rigo tool to download and install the software.

[albfneto]

See, seems that Fabio recovered SULFUR, made a 105 version. Please , update your repos, upgrade sulfur, then try to open it:

Code: Select all

$sudo equo update
$ sudo equo install sulfur --nodeps
$ sulfur


I use Rigo and commands, but i like Sulfur also...Thanks, Fabio!

[albfneto]

Please mark the topic as Solved.
In upgraded Sabayon, both Rigo and Sulfur are working.

[marinegundoctor]

I'm glad to see that I'm not the only one who prefers Sulfur over Rigo. I realize that Rigo is still being developed, but I find it (so far) to be slow and cumbersome compared to Sulfur. The command line is always nice, but I like browsing a list of grouped packages in a GUI. It's kind of like 'window shopping' for software
Back to my main point, I think that the main thing Rigo needs is the ability to build a que of software to install, then start installing with one button. This is the way it is done in Sulfur and is more efficient in my opinion. Rigo fails miserably at this task (as stated by others above).