an excellent demonstration on why mp-*fremantle-*-pr is a defective design and should get replaced by something more sane in CSSU, long term but ASAP.

A maybe silly but obvious idea: why not remove all the dependencies from mp-community-pr and instead have according "apt-get install" lines for each package in mp-community-pr's postinstall script? We could even add some fancy checks of a well-defined file like /.mp-community-pr_exclude_packages, to allow user to explicitly _not_ install certain stuff she doesn't want to get touched by CSSU upgrades.

@int_ua: afaik HAM doesn't support "OR", and it's hard to come up with a definition how to handle such "OR" when it comes to installation of a new mp*, which of the alternatives should get auto-installed?
Maybe 1.5 years ago we had a CSSU public meeting where merlin and me introduced an alternative concept for this problem, which involved patching HAM to handle the problems that arise. Checking for "PROVIDES" properties as well could introduce a method to have alternatives of which one is mandatory. A similar thing has been done for H-E-N depending on a property provided by hostmode kernel, and aiui for thumb kernel and CSSU-thumb.

bottom line: often devels and users bitch about "CSSU doesn't allow XY to `go into CSSU`" - what they mean is adding XY to CSSU MP, but CSSU should get rid of MP and asking for adding even new stuff is reactionary.


/j