[aur-general] broadcom-wl-dkms

2015-08-06 Thread Frank Vanderham
Folks, after a couple of years of maintaining broadcom-wl-dkms and enduring the Broadcom driver pains, I have finally switched to an Intel card. I don't mind staying as maintainer of this package, but since I can no longer test the driver myself, if there is a volunteer to take over, I'm okay with

[aur-general] Massive orphan request II

2013-07-08 Thread Frank Vanderham
>> That list is huge. I can certainly pick up a couple, but some of them look >> horribly outdated; is it an option to delete the ones that haven't been >> updated in - say - 12 months just to bring it down to a manageable number? >> It would be a waste of resources to spend time on a package that

[aur-general] Massive orphan request II

2013-07-08 Thread Frank Vanderham
>> That list is huge. I can certainly pick up a couple, but some of them look >> horribly outdated; is it an option to delete the ones that haven't been >> updated in - say - 12 months just to bring it down to a manageable number? >> It would be a waste of resources to spend time on a package that

[aur-general] Massive orphan request II

2013-07-08 Thread Frank Vanderham
>> Karol Blazewicz asked an excellent question. What's next, do you want to >> adopt them? >> > I may adopt a few but not all. I am hoping that by orphaning them, an active > maintainer may pick them up and fix/update them. That list is huge. I can certainly pick up a couple, but some of them look

[aur-general] Merge request: broadcom-wl-dkms, wireless-bcm43142-dkms, broadcom-wl6-dkms

2013-07-08 Thread Frank Vanderham
I understand, no problem! I adopted broadcom-wl-dkms. Would the people that had notifications on broadcom-wl-dkms (the one that was accidentally deleted) get those notifications again going forward? Otherwise I'll post something on the forums. Thanks! On Monday, July 08, 2013 07:50:33

[aur-general] Merge request: broadcom-wl-dkms, wireless-bcm43142-dkms, broadcom-wl6-dkms

2013-07-08 Thread Frank Vanderham
Discussion about the Arch User Repository (AUR)" < aur-general@archlinux.org> Cc: Date: Mon, 08 Jul 2013 12:34:23 +0800 Subject: Re: [aur-general] Merge request: broadcom-wl-dkms, wireless-bcm43142-dkms, broadcom-wl6-dkms On Sunday, July 07, 2013 22:26:20 Frank Vanderham wrote: >

Re: [aur-general] Merge request: broadcom-wl-dkms, wireless-bcm43142-dkms, broadcom-wl6-dkms

2013-07-07 Thread Frank Vanderham
Just a friendly reminder of this request I made a couple of days ago: please let me know if there is info missing or if there is a problem: On Fri, Jul 5, 2013 at 11:35 AM, Frank Vanderham wrote: > To clean up the naming and confusion around the various DKMS Broadcom > drivers out

[aur-general] Merge request: broadcom-wl-dkms, wireless-bcm43142-dkms, broadcom-wl6-dkms

2013-07-05 Thread Frank Vanderham
To clean up the naming and confusion around the various DKMS Broadcom drivers out on AUR, please perform the following: * merge the comments, history, etc. from wireless-bcm43142-dkms into broadcom-wl-dkms * merge the comments, history from broadcom-wl6-dkms into broadcom-wl-dkms This means that

[aur-general] [Merge Request] wireless-bcm43142-oneiric-dkms into wireless-bcm43142-dkms

2013-02-18 Thread Frank Vanderham
Could you please merge wireless-bcm43142-oneiric-dkms[0] into wireless-bcm43142-dkms[1]. The primary reason for the new package vs. updating the old is that the original package has "oneiric" in the name, which is an Ubuntu version name. I did not know this when I first build the PKGCONFIG; myself