modules dialog too complex ? #135
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
applications/manjaro-architect#135
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 ?
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 ...
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...
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...
changed the description