Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#18417 - {core} Make a "wifi-drivers" group

Attached to Project: Arch Linux
Opened by Matthew Bauer (matthewbauer) - Sunday, 21 February 2010, 03:57 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 22 June 2012, 04:40 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Aaron Griffin (phrakture)
Thomas Bächler (brain0)
Tom Gundersen (tomegun)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
Could there be a wifi-drivers group for people who would like to easily install all the open source wifi drivers available to Arch Linux?

This may be useful for making Arch-based live cds (so they can be run on multiple computers with different wifi devices).
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Friday, 22 June 2012, 04:40 GMT
Reason for closing:  Won't implement
Comment by Ionut Biru (wonder) - Sunday, 21 February 2010, 12:03 GMT
why do you want to install ALL open source drivers since only one will be used eventually?
Comment by Matthew Bauer (matthewbauer) - Sunday, 21 February 2010, 16:53 GMT
For LiveCDs and convenience, like xorg-input-drivers and xorg-output-drivers.
Comment by Greg (dolby) - Tuesday, 23 February 2010, 01:04 GMT
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.
Comment by Aaron Griffin (phrakture) - Tuesday, 23 February 2010, 22:27 GMT
Hmm, I don't have a strong opinion either way on this. Thomas, what do you think?
Comment by Thomas Bächler (brain0) - Tuesday, 23 February 2010, 22:37 GMT
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.
Comment by Matthew Bauer (matthewbauer) - Wednesday, 24 February 2010, 01:32 GMT
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
Comment by Aaron Griffin (phrakture) - Wednesday, 24 February 2010, 22:23 GMT
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
Comment by Thomas Bächler (brain0) - Wednesday, 24 February 2010, 22:54 GMT
It's the other way around: Users will want to install all wireless tools, but not all drivers.
Comment by Aaron Griffin (phrakture) - Wednesday, 24 February 2010, 23:09 GMT
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
Comment by Allan McRae (Allan) - Monday, 01 March 2010, 04:20 GMT
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.
Comment by Matthew Bauer (matthewbauer) - Tuesday, 02 March 2010, 22:52 GMT
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.
Comment by Allan McRae (Allan) - Saturday, 20 March 2010, 02:25 GMT
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.
Comment by Aaron Griffin (phrakture) - Monday, 22 March 2010, 18:06 GMT
@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)
Comment by Jelle van der Waa (jelly) - Friday, 17 June 2011, 22:48 GMT
i can't see how this would be usefull, much people install one wifi driver

Loading...