fapman was on list of broken packages due to rumours about having problems with some post/pre-install/remove scripts.

As fapman users since... Well, beginnings of times, I've had heated disxcussion about it on IRC with kerio - it resulted in me checking every package, that was rumored to *not* work properly with FAM (during discussion, it was realized that no one ever tried to confirm that rumours, just blindly forwarded them). Every single one of them worked perfectly, including all package's scripts, so I've put FUD stamp on those rumours.

As for other concerns some people have with fapman:

1. It have "autoremove" option checked by default, which is equivalent to doing apt-get autoremove, after every install/deinstall operation. Normally, it ensures, that we're getting rid of unnecessary packages, that were pulled automatically due to dependencies, and are no longer needed (because, for example, we deinstalled main package/metapackage/whatever).

Generally, without this, we would have mess of orphaned dependencies occupying our opt/root, so it's good thing to have this enabled. Still, in cases of system with utterly broken packages (dependencies), it may result in important things getting autoremoved. I've never experiwenced this myself, but I can imagine, that less carefull user with - again - broken system, can get it broken even further.

While it's rather related to USER_ERROR, it wouldn't hurt to have "autoremove" unchecked by default in fapman.

2. fapman use own catalogs - during installation, it imports catalogs from HAM, but later changes to one, doesn't result in syncing with another. It's *not* a bug - it's 100% intended feature, which proves itself useful, in many cases (ability to have different sources for HAM and FAM).

3. Famous "don't use FAM for system updates". Well, it originates in rumour about FAM having problems with some install scripts, which is FUD. Well, I use FAM for every CSSU update, since times, when it was faaar from being official - number of problems is 0. I even compare things with single device, that I always update via HAM - doing rsync comparision of files, configs, etc - delta is ZERO. Only one change is painfully long time of operating HAM.

Still, CSSU team supports only HAM way of updating (oficially), partially due to FUD about install scripts, and partially due to reasons, that I don't want to discuss here (are irrelevant as political, not technical).

I don't think that it require a"y changes in package, though - who wants to use HAM for CSSU does it, who wants to use FAM, acts so.

/Estel