using magneto

[LCN_UsesSabayon]

1st of all, I'd like to thank stupot (see reply below) because of my crazy question... Please, let me submit my question again:

Why magneto-gtk3 doesn't depend on rigo?

Indeed, when installing magneto-gtk3 following packages are also installed because of their dependency:
magneto-loader => magneto-core => rigo-daemon
But rigo isn't installed implicitly

So, without rigo installed, how using magneto for updating our OS? Option which launch frontend (rigo I guess) doesn't work because there is no frontend installed yet.

Installing rigo explicitly indeed solve this issue but I wonder if there is another solution (fixing dependency issue if lxnay thinks there is a dependency issue)

[Stupot]

Because it's the other way around. Rigo (the frontend) depends on rigo-daemon (the backend).

[albfneto]

Sulfur will be discontinued, substituted by Rigo Magneto will use Rigo daemon.

Rigo will be used in the future instead of sulfur.

if you not use Rigo, you will carry the command sudo equo upgrade, for upgrading.

If you plain to mantain Magneto, but no more use Rigo, you may remove only Rigo, with no deps removal:

Code: Select all

sudo equo remove --nodeps rigo

This will remove only Rigo, but Magneto will running, therefore, without Rigo, will will have only command for upgrade packages.

resuming, Rigo will be only frontend in the future. Magneto only INFORM the existing updates, not upgrade (nowsdays also, it uses Sulfur!).

Nowdays, Magneto uses sulfur for upgrades, in the future will use rigo.

[LCN_UsesSabayon]

Many thanks for this so clear answer!

I understand now that magneto can run without rigo frontend (rigo itself).
So I guess my following suggestion would improve magneto:

What about hidding entry which allows user to launch rigo from magneto notification icon when rigo isn't installed?
This entry is available in contextual menu

Before submitting this to dev team, I would lile to know community's advice

[Stupot]

Submit away. I don't really think it's all that necessary or a huge problem, but there is nothing wrong with polishing up the Sabayon package management tools.

[LCN_UsesSabayon]

Done: here