Gentoo Archives: gentoo-dev

From: Stroller <stroller@××××××××××××××××××.uk>
To: Gentoo Dev Mailing List <gentoo-dev@l.g.o>
Subject: [gentoo-dev] Wireless driver / firmware ebuilds & wireless-tools
Date: Sat, 21 May 2005 04:06:39
Message-Id: fc6c7531451ac46d62a222710259ffed@stellar.eclipse.co.uk
1 Hi,
2
3 I thought about filing another bug about this, but decided I'd rather
4 whine about it in public to get a better airing / flaming /
5 understanding of the issues.
6
7 Using a wireless network card under linux may require various
8 components:
9 - the hardware driver itself
10 - a firmware to be uploaded to the card via hotplug
11 - hotplug
12 - as I understand it: wireless-tools to actually configure the SSID,
13 WEP key
14 &c of the wireless network to be connected to.
15
16 Is my understanding of the last point incorrect?
17 Because it seems to me there's little point in emerging the ebuild for
18 a wireless network card unless it's going to be connected to a wireless
19 network, and in that case the least thing that's going to need setting
20 is the SSID & IP address.
21
22 Prism54 is the name of one such driver, and because it is being
23 incorporated into the main kernel tree there exists more than one
24 ebuild for it - one which includes the hardware driver module itself,
25 and one for one for users of the latest kernels who only require the
26 firmware.
27
28 These two ebuilds take a different approach to wireless-tools - one
29 requires it as a depend, the other does not:
30
31 $ emerge -pv prism54
32
33 These are the packages that I would merge, in order:
34
35 Calculating dependencies ...done!
36 [ebuild N ] sys-apps/hotplug-20040923 43 kB
37 [ebuild N ] net-wireless/prism54-firmware-1.0.4.3 91 kB
38 [ebuild N ] net-wireless/wireless-tools-27 +nls 0 kB
39 [ebuild N ] net-wireless/prism54-20050125 -pcmcia 74 kB
40
41 Total size of downloads: 210 kB
42 $ emerge -pv prism54-firmware
43
44 These are the packages that I would merge, in order:
45
46 Calculating dependencies ...done!
47 [ebuild N ] sys-apps/hotplug-20040923 43 kB
48 [ebuild N ] net-wireless/prism54-firmware-1.0.4.3 91 kB
49
50 Total size of downloads: 135 kB
51 $
52
53 I filed a bug <http://bugs.gentoo.org/show_bug.cgi?id=87197> about this
54 a few weeks ago, and was told:
55 "The firmware itself does not depend on wireless-tools for operation.
56 DEPEND/RDEPEND/PDEPEND in ebuilds are not for what you might
57 want to use along with the package in question - it is for technical
58 dependencies such as libraries and utilities."
59
60 Now, as I say, I can see few reasons to install the prism54 firmware &
61 not use wireless-tools - were you to use a Prism54 card in passive-mode
62 as a packet-sniffer then I suppose it's possible, but most users want
63 to `emerge prism54-firmware` and have it "Just Work (tm)".
64
65 Having been blown out on my bug I took it deeply personally, then
66 shrugged & forgot about it. Forgot about it, that is, until I went to
67 setup the wireless card in a freshly-installed laptop today:
68
69 $ emerge -pv acx100
70
71 These are the packages that I would merge, in order:
72
73 Calculating dependencies ...done!
74 [ebuild N ] net-wireless/wireless-tools-27 +nls 0 kB
75 [ebuild N ] net-wireless/acx100-0.2.0_pre8-r5 -pcmcia 275 kB
76
77 Total size of downloads: 275 kB
78 $
79
80 It seems to me that I could now file a bug about acx100 saying that it
81 "incorrectly depends upon wireless-tools" but - unless I'm
82 misunderstanding something pertinent - I still think this is the wrong
83 behaviour. Whether I'm installing a prism54 or an acx100 card in my
84 machine, I'm still going to need to iwconfig them to the right wireless
85 network.
86
87 The ebuild for the Ralink cards seems to feel the same way:
88
89 $ emerge -pv rt2500
90
91 These are the packages that I would merge, in order:
92
93 Calculating dependencies ...done!
94 [ebuild N ] net-wireless/wireless-tools-27 +nls 0 kB
95 [ebuild N ] net-wireless/rt2500-1.1.0_beta2-r1 +qt 286 kB
96
97 Total size of downloads: 286 kB
98 $
99
100 So, anyway, I don't intend for this posting to be a criticism of brix
101 for blowing me out on my bug, I just want to understand better. Can
102 anyone tell me if there's a logical reason for wireless-tools to be
103 treated differently by these 4 packages? If you "might want to use"
104 wireless-tools in almost every circumstance with the prism54-firmware &
105 this isn't covered by DEPEND/RDEPEND/PDEPEND, can we have a new
106 variable "YOU_MIGHT_WANT_TO_USE_DEPEND", please?
107
108 Stroller.
109
110 --
111 gentoo-dev@g.o mailing list

Replies