| Summary: | [net-wireless/ipw2100] ebuild for 0.41 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Cyril Jaquier <cyril.jaquier> |
| Component: | New packages | Assignee: | Mobile Herd (OBSOLETE) <mobile+disabled> |
| Status: | VERIFIED TEST-REQUEST | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| URL: | http://ipw2100.sourceforge.net | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
ipw2100-0.40 ebuild
ipw2100-0.41 ebuild |
||
|
Description
Cyril Jaquier
2004-04-15 01:25:19 UTC
Created attachment 29316 [details]
ipw2100-0.40 ebuild
I just create an ebuild for ipw2100-0.41. Works for me ! I haven't test WEP :( Created attachment 29406 [details]
ipw2100-0.41 ebuild
To install :
cp ipw2100-0.41.tar.gz /usr/local/portage
cd /usr/local/portage
tar xvfz ipw2100-0.41.tar.gz
FEATURES="-sandbox" ACCEPT_KEYWORDS="~x86" emerge ipw2100
Hey, i'll try to get the new version added soon. Couple things though: 1) Always attach just the ebuild as plaintext. Don't force people to download and untar something when the ebuild itself is really what people want to see. (: 2) USE flags: There's *WAY* too many USE flags already, and adding local flags for this one ebuild is not worth it, given how little time actually making those modules takes... Very few people are going to be on 100Mhz pentiums and using an intel wifi card, so the few CPU cycles seems acceptible to me to avoid forcing 2 new USE flags on people. I'm still pondering how to deal with the WEP issue (like when someone upgrades a kernel, then just re-emerges ipw2100). For now i'm just going to be adding a big old warning about needing to re-emerge hostap-driver too if you upgrade your kernel. Sorry but I'm using Gentoo for 1 month and a half. I just try to do the best to help the community... I really should (re)read the ebuild howto I think... 1. I made a .tar because ipw2100 needs hostap_crypt.h which I added in the files/ directory. I found some ebuilds doing that. I don't know if it's the correct way !? 2. I added these 2 USE flags because I didn't want to have the av5100 and pbe5 modules copied into my kernel modules directory. These 2 modules are compiled even if the USE flags aren't set. I have a lots to learn so I really appreciate your advices :) Thanks Okay, the hostap_crypt.h use makes sense, but next time just attach the ebuild, along with an explination of what you did/is needed for the ebuild to work correctly. I've just commited this minus the USE vars, if you really don't want 2 small modules around, you can remove them (the gains are far too minimal compared to the price off adding yet another 2 local USE vars). I've also added a check to make sure the hostap-driver modules are around, to make sure people re-emerge hostap-driver after a kernel upgrade. Thanks all. Please test and report back success/failures. SUCCESS !!! Closing. |
