View Single Post
Posts: 2,292 | Thanked: 4,135 times | Joined on Apr 2010 @ UK
#1
Originally Posted by Estel View Post
Examples of problems, please! It is exactly the argument that I tagged as "some imaginary problems that no one ever encountered".
OK.
Take fCamera 1.0.5-2 for example, it should conflict with kernel power, it does in HAM; all is well.
However, on both FAM and apt it doesn't conflict and allows installation, in most cases this causes a boot loop.

I believe there are other examples of this dependency mess all over Maemo, apt doesn't notice these conflicts and if apt doesn't FAM can't either.

To try and reproduce every application installation combination to find a conflict, would take a long time otherwise I would go through every package to prove a point. Why waste my time when HAM works?

Another example with screenshots attached below.
HAM shows one thing and FAM shows something else, this is the same system, both managers updated. I know which manager I trust to do the upgrade!

It's also very easy to install packages you shouldn't from different sections like libs for example. One without knowledge could easily end up in a mess. Only user packages should be available.
Also while mentioning sections, Nokia has disabled the user/hidden packages from being available in apt but they do show in HAM.

FAM uses the --allow-unauthenticated flag for all installs not the most secure method but at least it installs without any unnecessary security prompts

If you fully understand what is going on you are unlikely to have an issue. However, if your half asleep or forget to check everything with a fine toothcomb there is a possible dependency mess or reflash waiting around the corner.

Originally Posted by Estel View Post
I use apt-get and FAM for everything since dawns of time, and I never, ever touch HAM for any new N900's that I put my hands on. kernels, CSSU, whatever. Never had any problem, and never heard any details about what those problems may be.
Just because "you" haven't experienced issues doesn't mean there aren't any.

Originally Posted by Estel View Post
"FAM shaming" seems to live happily, god knows why. Maybe because there is no maintainer around, to defend own package against unfair accusations and outright lies.
I take offence to the fact you think I have no right to share my opinion and the fact you imply I would outright lie or jump on a "hate" band wagon.
I have no issues with the developer. He wanted to make a project in Qt and made FAM in the hope it will be useful. He has learned a lot along the way, just like I have, this is the FOSS spirit. Even the great MAG has learned stuff from FAM's sources.
I still believe it would have been better to make something else and provide fixes to HAM via CSSU instead, I am sure others would agree.

Originally Posted by Estel View Post
And don't even get me started at the "possible problems due to automatic autoremoval of unneeded packages" checkbox. It is freakin' optional thing, and complaining about it is as valid as accusing apt-get of having "autoremove" option (which is exactly the same thing that FAM uses with this checkbox). I sincerely hope that anyone using this know what she/he is doing.
The option is checked as default FFS. Anybody can install this package and use it (it's in extras BTW). I wouldn't expect a complete newbie to be able to get root and use autoremove without understanding it. I could expect someone finding FAM in the repos and using it without knowing what the options actually do.

Yes, potentially the system has all ready been slightly broken if there's an issue, however, autoremove will just make it worse not better.
Attached Images
  
__________________

Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -


Before posting or starting a thread please try this.
 

The Following 18 Users Say Thank You to sixwheeledbeast For This Useful Post: