Bug 28179

Not only allow - i think it should by default install it unless user deselect it in advanced package selection.

Alternatively only if a wifi module is detected, if that is reliable and easy to implement.

Also see https://bugs.mageia.org/show_bug.cgi?id=28155#c4

And I think this is important to try to get into mga8 ISOs as such hardware is out there.

CC: (none) => fri
Priority: Normal => High
Target Milestone: --- => Mageia 8

Installer enhancement, or add dependency to drakx-net-applet?

Component: RPM Packages => Installer

the proper place is to add it to meta-task as part of default install without forcing it on systems... ( think servers that does not need wifi )

Source RPM: drakx-net-2.54-1.mga8.src.rpm => meta-task

(In reply to Thomas Backlund from comment #3)
> the proper place is to add it to meta-task as part of default install
> without forcing it on systems... ( think servers that does not need wifi )

meaning so it can be removed if admin wants a cleaner install...

but we need to check the orphans routine so it does not remove it

of course this brings us to the next point... firmwares..

that means we should always install all firmware as most usb plugs need them and so on...

(In reply to Morgan Leijström from comment #1)

> Alternatively only if a wifi module is detected, if that is reliable and
> easy to implement.
>

This part we already do, but it does not cover times when the wifi module is plugged after install...

a little chicken and egg problem :)

This should really have remained as the original bug 28155.
I repeat a comment I made there: we should always install WiFi "in case". It is almost normal today. 
>> Alternatively only if a wifi module is detected, if that is reliable and
>> easy to implement.
> This part we already do
Good! That should cover most cases. Live & Classic ISOs?

> it does not cover times when the wifi module is plugged after install...
@Ben: was this your case? Did you perhaps have only 1 USB slot for the installation, none for the plug-in WiFi?

I have always thought that all installations should (may already) recommend before starting the importance of a working Internet connection - if possible. That would prompt pluggable WiFi-ers to stick it in, when it would be discovered in time.

But I think this is best:
(In reply to Thomas Backlund from comment #3)
> the proper place is to add it to meta-task as part of default install
> without forcing it on systems... ( think servers that does not need wifi )
> meaning so it can be removed if admin wants a cleaner install
Certainly if it worries anyone, it can be removed manually (but not by the "remove unnecessary h/w support" option).
This multi-desktop M7 ex-Classic ISO system has wpa_supplicant, but no WiFi...

CC: (none) => lewyssmith

Another idea is to install it if *wired* interface is *not* found.
Then it will "never" be installed on servers, and no tom computers with both types of interfaces.
But will be installed on laptops with no wired - regardless of modem is plugged in or not.

I had thought of that too, so second the idea; accepting that it is installed if WiFi h/w *is* found. But it would be a bit more complicated.

(In reply to Lewis Smith from comment #6)

> 
> > it does not cover times when the wifi module is plugged after install...
> @Ben: was this your case? Did you perhaps have only 1 USB slot for the
> installation, none for the plug-in WiFi?
> 


yes single usb port

To summarise what looks like agreement:
1. It is essential for most things (except where you have to live with the installed system/installation medium as-is) to have a working Internet connection; ideally during installation (on-line repos etc); vital afterwards.

2. If WiFi h/w is detected during installation, it is catered for.

3. WiFi-only users with pluggable USB dongle who cannot plug it in before installation (see previous comment), so it gets noticed & taken into account, currently find themselves with no WiFi software - hence Internet - so cannot install it!
[Surely there is a way of getting it off the installation ISO? Perhaps this is what is in Errata - on-line...]

4. We can cover this situation by one of:

- *Always* install WiFi software: "the proper place is to add it to meta-task as part of default install". People who do not want it can either deselect it from Classic ISO install; or remove it subsequently. (It should NOT be removed by the installer along with other unnecessary support). This looks the easiest solution.

- Install it if no Ethernet is found (and not already installed because WiFi is found). (It should NOT be removed by the installer along with other unnecessary support). This looks more elegant, probably slightly more work.

Assigning to the tools group; CC'ing Martin since it may affect ISO content.

Assignee: bugsquad => mageiatools
Severity: enhancement => major
Summary: allow CI.isos to install wpa_supplicant where no wired LAN is an option, if WIFI module is available => Allow ISOs to install wpa_supplicant where no wired LAN or WIFI module is present at installation
CC: lewyssmith => mageia

An entry in rpmsrate of

  HW_CAT("network/wireless") || !HW_CAT("network/") wpa_supplicant

might do the job, although that still leaves a problem with missing firmware.