[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#758116: Allow to select Blends selection during installation - just "DE", "Web server", "Mail server" is NOT enough

Hi Wolfgang,

On 17.05.2016 11:52, Wolfgang Schweer wrote:
> On Tue, May 17, 2016 at 08:52:32AM +0200, Ole Streicher wrote:
>> On 17.05.2016 02:13, Cyril Brulebois wrote:
>>> I'm not sure how reasonable it is to have such a long list of meta
>>> packages in the installer. See attached tasksel-gtk-greyscale.png for
>>> the initial display with the graphical installer, and attached
>>> tasksel-text-greyscale.png for the text mode installer.
>> I don't see it problematic as it is in the moment: The list is not too
>> long: Even if it does not fit on one screen, the rest is visible with
>> just one scroll, and this is indicated by the scroollbar. And I don't
>> think that the number of options is too much (it shouldn't be much more,
>> however).
> I'm just wondering if the blend install could be implemented one level 
> higher using the ISO image isolinux menu structure.

The advantage of the boot menu would be that in the tasksel step, one
could select individual tasks for the selected blend, and not just a
default installation. This would, however, still not allow a selection
on the package level as it was requested for NeuroDebian.

This would however add all the 13 blends to the boot menu, making this
much more crowded. And it would be impossible to select two blends at
the same time (say: science and astro).

It would also feel the Blends as being more separated from Debian
itself: you could either install "Debian", or one of the Blends. The
tasksel approach would make clear what they are in reality: a
comprehensive selection of packages and (maybe) configuration for a
specific need.

I would opt for the current solution of having it in tasksel and not in
the boot menu; especially since it is now already implemented (after two
years of discussion), with all the infrastructure and needed changes in
blends-dev in place. IMO the better solution is now to push tasksel for
a better structured package selection.

> All blends would need their own debian-<blend_name>-install-udeb and 
> debian-<blend_name>-profile-udeb; these need to be on all official 
> Debian installation media if these should work like the mini.iso image. 

Extrapolating the slow development on the common blends-install subject
in the last years (especially in bug #758116), I would not expect this
to happen before the next release. The tasksel approach also has the
advantage that it is semi-centralized: all Blends get a default install
of all their tasks, and they may adjust this in their debian-<blend>
package if needed.

Best regards


Reply to: