new to equo, I think I like it, but...

[joe3]

I recently learned of the existence of equo... OK so I live under a rock or something...<grin> I have however been using emerge for sometime. I have no objections to using precompiled binaries but I'm concerned that they could conflict with the software I already have???

My biggest concern is if it's not recommended to use binary packages to update something that had been originally been emerged from a non-binary ebuild, -OR- If you can get into trouble letting emerge update with a non-binary ebuild something that had been installed via equo, then what happens when I forget which way I installed something and upgrade it with the other command line tool???

As it happens, I just wound up using emerge to get firefox 3.0.1

I had developed a problem where the old firefox 2.0.0.11 on my laptop stopped working complaining about some lib... I looked at what equo search for that lib (forgot name, used clipboard to do search...) but it didn't find anything. I did a search for firefox and everything I saw said 2.0.0.11 and I wasn't sure of the results pf reinstalling a binary version of something that emerge had compiled on my machine so I decided to use emerge --ask mozilla-firefox to find out if it wanted to fix said lib... and lo and behold I saw something about 3.0.1 patches... needless to say I immediately said yes and soon repeated the process on my desktop.

Is it _SAFE_ to switch back and forth between the two methods as long as I remember to:
emerge --sync
before emerging anything and to:
equo update
before I use equo install?????????

--
joe3

[wolfden]

Should pick one and stick with it. You are probably using different flags than entropy if you are using portage anyway.

[joe3]

Kind of figures. I like the relative speed of equo, and I find it's simplified syntax much easier to understand... But I've already installed several packages with # emerge

So perhaps I need to wait until I next do a new install of sabayon to begin using equo???

Or can I safely simply switch to using equo and let the entropy default settings handle the flags from now on???

As far as flags go, I don't really understand their use, So I've always just used whatever default flags get set when you simply

# emerge -a ${packagename}

--
joe3

[Stupot]

If you haven't changed any flags in your make.conf file, then go ahead and start using equo. You should be just fine.

[Darksurf]

I usually use both, and I've never had a problem. Somethings are just generic while others are specifically compiled for my CPU.
But I haven't ever had any problems. Currently I only use entropy so I can stay on top of testing for stability and issues so that I can report
them upstream to keep you guys stable and up-to-date. Equo is definitely nice and waaay faster. And its getting better and better with
new features and ideas all the time. There is still some possibilities that things may conflict but I haven't encountered any problems yet.
As they are both smart applications that pull dependencies of the apps.

[joe3]

OK If I get the gist of all this is that most likely I CAN get away with using both depending on if I want a custom compiled version. Especialy IF I never actualy play with the flag settings???

So I can likely get away with MOSTLY using equo, but occasionaly useing emerge...

Life is good!

But I also wonder about removing packages...

According to man emerge unmerging packages is a bit risky for inexperianced users, and while the depclean is a bit safer it too comes with strong warnings...

equo --help is a bit less verbose so I gotta wonder... Is:

equo remove package

any safer for the inexperianced who don't really know what to watch for in the output of a --ask option????

--
joe3

[Darksurf]

yeah its safe. And if you are worried about emerge -C (emerge --uninstall as you could call it) its safe. If you ever question yourself about
removing something you should probably ask what is it you are removing. Look it up. see if you use it or not. If you are still worried after a removal
use "revdep-rebuild" it checks dependencies to see if something needed was removed and then tries to re-install it to fix the issue. Sometimes, it goes
a little overboard and is a little too safe going through extra stuff that isn't really needed.. such as recompiling KDE stuff. But Its just trying to protect you.
You can easily over look that an just recompile what is needed without recompiling KDE stuff. Just look at the list of what It says needs recompiling and pickout
the packages needed and just emerge them.

[Stupot]

When you uninstall with equo, it keeps track of reverse dependencies for you. So, if you look at what uninstalling a package using equo would do, it will show you that it will uninstall that package and every package that depends on the one you are trying to uninstall.

Uninstalling with emerge does not keep track of that.

I would say that is the main difference between uninstalling with the two systems.