Summary: | Move madwifi headers into madwifi-ng-tools | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Daniel Drake (RETIRED) <dsd> |
Component: | New packages | Assignee: | Steev Klimaszewski (RETIRED) <steev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gengor, mobile+disabled, togge.gentoo, uberlord |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
madwifi-ng-0.9.3-r4.patch
madwifi-ng-tools-0.9.3-r1.patch hostapd-0.4.9-r1.patch hostapd-0.5.7-r1.patch wpa_supplicant-0.5.7-r1.patch |
Description
Daniel Drake (RETIRED)
2007-05-21 19:27:12 UTC
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. Created attachment 119968 [details, diff]
madwifi-ng-0.9.3-r4.patch
Patch: madwifi-ng-0.9.3-r3.ebuild -> madwifi-ng-0.9.3-r4.ebuild
Created attachment 119970 [details, diff]
madwifi-ng-tools-0.9.3-r1.patch
Patch: madwifi-ng-tools-0.9.3.ebuild -> madwifi-ng-tools-0.9.3-r1.ebuild
Created attachment 119972 [details, diff]
hostapd-0.4.9-r1.patch
Patch: hostapd-0.4.9.ebuild -> hostapd-0.4.9-r1.ebuild
Created attachment 119973 [details, diff]
hostapd-0.5.7-r1.patch
Patch: hostapd-0.5.7.ebuild -> hostapd-0.5.7-r1.ebuild
Created attachment 119975 [details, diff]
wpa_supplicant-0.5.7-r1.patch
Patch: wpa_supplicant-0.5.7.ebuild -> wpa_supplicant-0.5.7-r1.ebuild
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. the madwifi side of things is done. Now madwifi-ng-tools don't emerge due to file collisions with madwifi-ng. A blocker against older versions? (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. (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? all fixed, thanks. |