Arch Linux

why do you want to install ALL open source drivers since only one will be used eventually?

For LiveCDs and convenience, like xorg-input-drivers and xorg-output-drivers.

You might want to continue what i started here:  FS#12890 
I doubt noone else will and i am no longer using Arch so dont mean to do it myself.

Hmm, I don't have a strong opinion either way on this. Thomas, what do you think?

I was once planning to make the following groups:
- base (we have that already)
- base-devel (that too)
- base-networking (ppp, netcfg, ssh and stuff, remove some of it from base)
- base-wireless (wireless_tools, crda, iw, wpa_supplicant, wpa_actiond, wireless firmware/drivers, remove all of them from base)
I never got to it though.

Could you have a group inside of another group; so there could be a base group that has the base-wireless group inside of it?

Here's a preliminary list of some packages that could be included:

ar9170-fw
ipw2100-fw
ipw2200-fw
iwlwifi-1000-ucode
iwlwifi-3945-ucode
iwlwifi-4965-ucode
iwlwifi-5000-ucode
iwlwifi-5150-ucode
iwlwifi-6000-ucode
rt2x00-rt61-fw
rt2x00-rt71w-fw
rt2870usb-fw
tiacx
tiacx-firmware
madwifi
zd1211-firmware

Does a "base-wireless" group not satisfy the request? I can't see a reason something like a livecd would need to install drivers but not the utilities to actually USE the drivers

It's the other way around: Users will want to install all wireless tools, but not all drivers.

Right, but in the context of this bug (a request for a group containing ALL wireless drivers), the assumption is that we're talking about a live cd or some sort of "default" environment made to work on a variety of hardware. You still need the wireless tools for those environments

A group that the majority of users will not ever need to use seems a bit overkill to me. Why not take an approach like archboot does and just have a PKGBUILD with a massive list of dependencies to install.

However, if it decided to implement this then we will need:
1) name for group (base-wireless-drivers?)
2) complete list of drivers to include (is the list above complete?)
Then I commit the change to trunk and add the packages to the "unimportant rebuild list" page.

This is true, a majority of people don't need it.

But let's say a new driver is added, we'd have to update the archboot lists of wireless drivers on other projects and this can be tedious. And it doesn't seem like it would be very hard to add the group.

Unassigning me. I can do the commits once a group name and list of packages has been decided upon but will not be doing the leg work for this bug.

@Allan: Regarding groups that no one will ever need. We have xorg-video-drivers, kde-l10n, thunderbird-i18n, and lib32. We have many groups that are groups of garbage that no one will ever need - the most relevant one here being xorg-video-drivers.

As for the group name, if we're adding base-wireless for wireless tools, I see nothing wrong with base-wireless-drivers (considering we have xorg-video-drivers)

i can't see how this would be usefull, much people install one wifi driver