| 1 |
On May 21, 2005, at 6:25 am, Doug Goldstein wrote: |
| 2 |
> Stroller wrote: |
| 3 |
>> Hi, |
| 4 |
>> |
| 5 |
> ..... farrrrr tooooo long............. |
| 6 |
|
| 7 |
Yeah, sorry... I've always been pedantic. It's a real hard habit to |
| 8 |
shift. |
| 9 |
|
| 10 |
> In summary and simple conclusion, yes you are wrong. So that makes 2 |
| 11 |
> out |
| 12 |
> of the 4 or 5 active Mobile herd devs who say you're wrong. |
| 13 |
|
| 14 |
Sorry again. Maybe I didn't make myself clear. I didn't mean to say in |
| 15 |
my posting "I'm right", but rather I intended to ask: |
| 16 |
|
| 17 |
Surely a user who emerges prism54-firmware will depend upon |
| 18 |
wireless-tools? |
| 19 |
|
| 20 |
> "The firmware itself does not depend on wireless-tools for operation. |
| 21 |
> DEPEND/RDEPEND/PDEPEND in ebuilds are not for what you might |
| 22 |
> want to use along with the package in question - it is for technical |
| 23 |
> dependencies such as libraries and utilities." |
| 24 |
|
| 25 |
Ok... so you're saying that the way to resolve this is to have a |
| 26 |
variable called USER_WILL_DEPEND or similar? |
| 27 |
|
| 28 |
> ....The firmware, which in 2 of these |
| 29 |
> cases are in seperate packages, do not depend on wireless-tools. |
| 30 |
|
| 31 |
Y'see I'm just not getting why not. |
| 32 |
|
| 33 |
A user can install Gentoo, compile the prism54 drivers in to his |
| 34 |
kernel, emerge the prism54-firmware ebuild and not have |
| 35 |
wireless-tools. Yet having emerged the prism54-firmware the user has |
| 36 |
indicated to Portage that, yes, indeed, he intends upon using a |
| 37 |
wireless network card. |
| 38 |
|
| 39 |
As I understand it, the firmware can be uploaded to a wireless card |
| 40 |
without the wireless-tools, but nothing useful can be done with either |
| 41 |
the wireless card or the firmware without it. |
| 42 |
|
| 43 |
Are you telling me this understanding is wrong? |
| 44 |
|
| 45 |
The distinction between driver & firmware kinda dawned on me whilst |
| 46 |
writing my original email, but I don't the practical implications. The |
| 47 |
user needs wireless-tools in either case, right? |
| 48 |
|
| 49 |
Is it the case instead that using DEPEND, RDEPEND or PDEPEND would |
| 50 |
break something else if used to indicate the user's need? Hence a |
| 51 |
variable called USER_WILL_DEPEND would be more suitable? |
| 52 |
|
| 53 |
This is just melting my head, because I just don't see what I've got |
| 54 |
wrong here - both you & brix have told me so, so you must be right. |
| 55 |
Could you please explain more slowly for me? |
| 56 |
|
| 57 |
|
| 58 |
> And for |
| 59 |
> a last example which I just thought of... ndiswrapper acts the sameway. |
| 60 |
> Considering the Windows drivers are more of a "firmware" and |
| 61 |
> ndiswrapper |
| 62 |
> is the driver. |
| 63 |
|
| 64 |
Mostly for ideological reasons I tend to ignore NDISwrapper, but I see |
| 65 |
that emerging it pulls in wireless-tools. This seems correct and |
| 66 |
sensible to me - by emerging NDISwrapper the user has indicated that he |
| 67 |
intends on installing a wireless card (right?), so the ebuild provides |
| 68 |
him with the tools he will need to set its SSID & WEP key. |
| 69 |
|
| 70 |
Stroller. |
| 71 |
|
| 72 |
-- |
| 73 |
gentoo-dev@g.o mailing list |
Archives