Split installer to simple and advanced version

Chrysostomus commented

2017-03-01 04:33:51 +00:00

(Migrated from gitlab2.manjaro.org)

There have been requests to simplify the installer. One option would be to split the installer to two variants. If we do this I suggest waiting until installer is restructured.

For the simple installer, we could

drop git profile installation and unconfigured desktops
drop networking and multimedia menu
unite vconsole and Xorg keymap setting
automate fstab generation, mkinitcpio and some other stuff in the exit
merge base installation and profile installation?

There have been requests to simplify the installer. One option would be to split the installer to two variants. If we do this I suggest waiting until installer is restructured. For the simple installer, we could - drop git profile installation and unconfigured desktops - drop networking and multimedia menu - unite vconsole and Xorg keymap setting - automate fstab generation, mkinitcpio and some other stuff in the exit - merge base installation and profile installation?

Chrysostomus commented

2017-03-01 04:35:47 +00:00

(Migrated from gitlab2.manjaro.org)

Maintaining 2 versions would be a lot of extra work though

Chrysostomus commented

2017-03-01 05:19:10 +00:00

(Migrated from gitlab2.manjaro.org)

To make it work, we could merge some simplifications to main version, keep differences to the level of main menu. We could then have just have two separate main menu functions, maybe chosen at runtime with a command line switch.

To ease this, we could move networking capabilities menu and multimedia menu under the unconfigured desktops menu. Then the difference could be just where the graphics menu takes you: submenu or straight to profile selection. It could actually be done within one function even...

To make it work, we could merge some simplifications to main version, keep differences to the level of main menu. We could then have just have two separate main menu functions, maybe chosen at runtime with a command line switch. To ease this, we could move networking capabilities menu and multimedia menu under the unconfigured desktops menu. Then the difference could be just where the graphics menu takes you: submenu or straight to profile selection. It could actually be done within one function even...

papajoke commented

2017-03-01 10:57:22 +00:00

(Migrated from gitlab2.manjaro.org)

It should be able to adapt to a community iso, without dialogue for soft part.
For example call by:

manjaro-architect --desktop=i3 [--arch=i386] [--init=systemd] [--minimal] [--nogrub] --extra="dev-tools,gnome-extra"

if "param" present, not show menu but directly use param

Add also for hard for Automated tests and Advanced users

manjaro-architect --dsys="/dev/sda5" --dhome="/dev/sda6" [-f ext4] ...

It should be able to adapt to a community iso, without dialogue for soft part. For example call by: manjaro-architect --desktop=i3 [--arch=i386] [--init=systemd] [--minimal] [--nogrub] --extra="dev-tools,gnome-extra" if "param" present, not show menu but directly use param Add also for hard for Automated tests and Advanced users manjaro-architect --dsys="/dev/sda5" --dhome="/dev/sda6" [-f ext4] ...

Chrysostomus commented

2017-03-01 11:14:02 +00:00

(Migrated from gitlab2.manjaro.org)

interesting idea, though quite different than what I suggested.

papajoke commented

2017-03-01 11:24:55 +00:00

(Migrated from gitlab2.manjaro.org)

Architecture is the same, exit the static menus, use dynamic menus
After we are free to automate things

Architecture is the same, exit the static menus, use dynamic menus After we are free to automate things

Chrysostomus commented

2017-03-01 11:32:00 +00:00

(Migrated from gitlab2.manjaro.org)

Aah! You mean that we would generate menus dynamically based on the command line options? So it is a new idea to fulfill the same goal?

Rows
Columns

Split installer to simple and advanced version #77