Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 179348
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Steev Klimaszewski <steev@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Daniel Drake <dsd@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
madwifi-ng-0.9.3-r4.patch madwifi-ng-0.9.3-r4.patch patch Gordon Malm 2007-05-22 09:04 0000 1.02 KB Details | Diff
madwifi-ng-tools-0.9.3-r1.patch madwifi-ng-tools-0.9.3-r1.patch patch Gordon Malm 2007-05-22 09:05 0000 913 bytes Details | Diff
hostapd-0.4.9-r1.patch hostapd-0.4.9-r1.patch patch Gordon Malm 2007-05-22 09:06 0000 951 bytes Details | Diff
hostapd-0.5.7-r1.patch hostapd-0.5.7-r1.patch patch Gordon Malm 2007-05-22 09:07 0000 852 bytes Details | Diff
wpa_supplicant-0.5.7-r1.patch wpa_supplicant-0.5.7-r1.patch patch Gordon Malm 2007-05-22 09:07 0000 1.05 KB Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 179348 depends on: Show dependency tree
Bug 179348 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2007-05-21 19:27 0000 
Currently the madwifi-ng ebuild installs the /usr/include/madwifi headers used
by wpa_supplicant and hostapd. This means that wpa_supplicant has to
conditionally depend on madwifi-ng, which is in itself nasty because madwifi-ng
has dependencies on kernel stuff -- this is an inconvenience when building
release media etc.

I think the headers should be installed by the madwifi-ng-tools ebuild and
wpa_supplicant/hostapd dependencies should be updated.

------- Comment #1 From Gordon Malm 2007-05-22 09:03:17 0000 ------- 
I just whipped up some patches to do as requested in this bug.  They work for
me with the exception of hostapd-0.5.7-r1.patch which I did not test.

------- Comment #2 From Gordon Malm 2007-05-22 09:04:24 0000 ------- 
Created an attachment (id=119968) [details]
madwifi-ng-0.9.3-r4.patch

Patch: madwifi-ng-0.9.3-r3.ebuild -> madwifi-ng-0.9.3-r4.ebuild

------- Comment #3 From Gordon Malm 2007-05-22 09:05:20 0000 ------- 
Created an attachment (id=119970) [details]
madwifi-ng-tools-0.9.3-r1.patch

Patch: madwifi-ng-tools-0.9.3.ebuild -> madwifi-ng-tools-0.9.3-r1.ebuild

------- Comment #4 From Gordon Malm 2007-05-22 09:06:24 0000 ------- 
Created an attachment (id=119972) [details]
hostapd-0.4.9-r1.patch

Patch: hostapd-0.4.9.ebuild -> hostapd-0.4.9-r1.ebuild

------- Comment #5 From Gordon Malm 2007-05-22 09:07:02 0000 ------- 
Created an attachment (id=119973) [details]
hostapd-0.5.7-r1.patch

Patch: hostapd-0.5.7.ebuild -> hostapd-0.5.7-r1.ebuild

------- Comment #6 From Gordon Malm 2007-05-22 09:07:34 0000 ------- 
Created an attachment (id=119975) [details]
wpa_supplicant-0.5.7-r1.patch

Patch: wpa_supplicant-0.5.7.ebuild -> wpa_supplicant-0.5.7-r1.ebuild

------- Comment #7 From Gordon Malm 2007-05-22 09:40:20 0000 ------- 
In the case of hostapd/wpa_supplicant ebuilds these changes should probably
just go into the existing ebuilds instead of a rather meaningless revbump. 
Only submitted the patches this way for consistency/testing/etc.

------- Comment #8 From Stefan Schweizer 2007-05-23 16:07:52 0000 ------- 
the madwifi side of things is done.

------- Comment #9 From Togge 2007-05-24 05:31:42 0000 ------- 
Now madwifi-ng-tools don't emerge due to file collisions with madwifi-ng. A
blocker against older versions?

------- Comment #10 From Gordon Malm 2007-05-24 06:22:47 0000 ------- 
(In reply to comment #9)
> Now madwifi-ng-tools don't emerge due to file collisions with madwifi-ng. A
> blocker against older versions?
> 

That was left out in the cvs commit.  There is also a format error in the einfo
messages at the end.

------- Comment #11 From Stefan Schweizer 2007-05-24 08:56:35 0000 ------- 
(In reply to comment #9)
> Now madwifi-ng-tools don't emerge due to file collisions with madwifi-ng. A
> blocker against older versions?


A blocker is a bad thing because most users do not know how to correctly handle
it. Besides it braks automated updates.

Maybe we can remove the conflicting files in preinst?

------- Comment #12 From Stefan Schweizer 2007-06-19 07:54:48 0000 ------- 
all fixed, thanks.
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug