modules dialog too complex ? #135

Closed
opened 2017-03-27 14:25:55 +00:00 by papajoke · 4 comments
papajoke commented 2017-03-27 14:25:55 +00:00 (Migrated from gitlab2.manjaro.org)

for a simple user modules dialog is too complex

can you detect if somes modules are needed ?
Add more body text ? or short description with item ?
auto add KERNEL-headers if virtualbox-host selected ?

# Choose wanted kernel modules
local invb="off"
[[ $(</sys/class/dmi/id/product_name) == "VirtualBox" ]] && invb="on"
# other detect ?

DIALOG " $_ChsAddPkgs " --checklist "\n$_UseSpaceBar\n " 0 0 12 \
  "KERNEL-headers" "for compile kernel" off \
  "KERNEL-acpi_call" "enables calls to ACPI" on \
  "KERNEL-ndiswrapper" "Windows Network Drivers" on \
  "KERNEL-broadcom-wl" "wifi driver BCM43142" off \
  "KERNEL-r8168" "Realtek 8168 network cards" off \
  "KERNEL-rt3562sta" "Ralink RT3562 PCI WLAN" off \
  "KERNEL-tp_smapi" "ThinkPad's SMAPI functionality" off \
  "KERNEL-vhba-module" "emulates SCSI devices" off \
  "KERNEL-virtualbox-guest-modules" "install in virtualbox" "${invb}" \
  "KERNEL-virtualbox-host-modules" "use virtualbox" off \
  "KERNEL-spl" "Solaris Porting Layer" off \
  "KERNEL-zfs" "Zettabyte File System" off 2>/tmp/.modules || return 0
for a simple user modules dialog is too complex can you detect if somes modules are needed ? Add more body text ? or short description with item ? auto add KERNEL-headers if virtualbox-host selected ? # Choose wanted kernel modules local invb="off" [[ $(</sys/class/dmi/id/product_name) == "VirtualBox" ]] && invb="on" # other detect ? DIALOG " $_ChsAddPkgs " --checklist "\n$_UseSpaceBar\n " 0 0 12 \ "KERNEL-headers" "for compile kernel" off \ "KERNEL-acpi_call" "enables calls to ACPI" on \ "KERNEL-ndiswrapper" "Windows Network Drivers" on \ "KERNEL-broadcom-wl" "wifi driver BCM43142" off \ "KERNEL-r8168" "Realtek 8168 network cards" off \ "KERNEL-rt3562sta" "Ralink RT3562 PCI WLAN" off \ "KERNEL-tp_smapi" "ThinkPad's SMAPI functionality" off \ "KERNEL-vhba-module" "emulates SCSI devices" off \ "KERNEL-virtualbox-guest-modules" "install in virtualbox" "${invb}" \ "KERNEL-virtualbox-host-modules" "use virtualbox" off \ "KERNEL-spl" "Solaris Porting Layer" off \ "KERNEL-zfs" "Zettabyte File System" off 2>/tmp/.modules || return 0
oberon commented 2017-03-27 15:03:07 +00:00 (Migrated from gitlab2.manjaro.org)

It will be difficult to decide for the user, which modules they might need or not... We could maybe at least add an infobox about what extramodules are and let the user either open the choice or just continue without ...

It will be difficult to decide for the user, which modules they might need or not... We could maybe at least add an infobox about what extramodules are and let the user either open the choice or just continue without ...
oberon commented 2017-03-27 15:08:46 +00:00 (Migrated from gitlab2.manjaro.org)

What would maybe also be good to try simplify/clarify is the "common packages" moment.
I think it would be more logical to move yaourt+base-devel there and offer it for installation only in case the selected profile has not installed it already - most profiles do. Question is just how to determine if a group has been installed. I guess we'd have to spot one or the other specific package, maybe just simply yaourt 😉
In any case the "common packages" page can be improved with some more informative text...

What would maybe also be good to try simplify/clarify is the "common packages" moment. I think it would be more logical to move **yaourt+base-devel** there and offer it for installation only in case the selected profile has not installed it already - most profiles do. Question is just how to determine if a group has been installed. I guess we'd have to spot one or the other specific package, maybe just simply **yaourt** :wink: In any case the "common packages" page can be improved with some more informative text...
Chrysostomus commented 2017-05-09 11:56:48 +00:00 (Migrated from gitlab2.manjaro.org)

I think adding descriptions would make sense.
I think we could autodetect at least zfs (check if user mounted anything as zfs), virtualbox (parse output of dmidecode), and maybe broadcom and thinkpad.

Problem is, I don't know what many of these actually do...

I think adding descriptions would make sense. I think we could autodetect at least zfs (check if user mounted anything as zfs), virtualbox (parse output of dmidecode), and maybe broadcom and thinkpad. Problem is, I don't know what many of these actually do...
yochananmarqos1 commented 2024-05-05 19:28:55 +00:00 (Migrated from gitlab2.manjaro.org)

changed the description

changed the description
yochananmarqos1 (Migrated from gitlab2.manjaro.org) closed this issue 2024-05-05 19:28:55 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
applications/manjaro-architect#135
No description provided.