Hi Michael, On 10.12.2016 13:18, Michael Biebl wrote: > While I have no opninion on whether blend-tasks is important enough to > have installed by default, I would urge to revisit the idea to (mis)use > the package priority to achieve that.
That is the standard way how tasksel gets its menu: tasksel-data is marked as "important" and that way it finds its way onto the installer image. So, all arguments you have here are also valid for the default tasks. If we think this is wrong, we should get a completely different solution here -- which is IMO outside of the scope of this bug. > If a package was pulled in by debootstrap because of its priority, it's > marked as manually installed. > This is usually bad, because say later on you decide that you want to > change the name of the package or implement this differently, the > manually installed package sticks around. But this problem is true for all manually installed package, right? So, a manually installed iceweasel would have a renaming problem as well. Couldn't it be solved by a transitional package? I would also consider this as not being release critical. The current solution would also have the advantage that people who actually hate the blends task list (like Holger Levsen: "I will get used to type 'apt remove blends-tasks' as well.") have the possibility to remove that from the tasks selection list. So, this would probably have more acceptance than a solution where the blends tasks are glued into the main task selection. Best regards Ole
