[Chris Hofstaedtler] > I don't know of any way of removing packages on upgrades from users > systems, but at least the packages could become empty themselves.
Perhaps we can turn them into empty packages, add a description specifying that they are transitional packages, and in the next release add a conflict from a often installed package on these transitional packages to get them removed? Or will it work to let the transitional discover package depend on some other package first, and then let the other package conflict with discover in the next release? Personally I believe isenkram-cli can take over for discover, I wrote it to take over its task, and would be happy to add a conflict when the time is right. -- Happy hacking Petter Reinholdtsne
