[haiku-development] Moving wpa_supplicant back in-tree or forking it?

  • From: Alexander von Gluck IV <kallisti5@xxxxxxxxxxx>
  • To: Haiku Development <haiku-development@xxxxxxxxxxxxx>
  • Date: Sun, 02 Aug 2015 09:12:51 -0500

I've wanted to throw this topic out here for some time.

We have a "lot" of patches to wpa_supplicant to draw windows,
do password management, and other stuff.

https://github.com/haikuports/haikuports/blob/master/net-wireless/wpa_supplicant/patches/wpa_supplicant-2.0.patch

Right now we keep wpa_supplicant as a recipe with a very long patch.
I think the patches will likely never be accepted upstream.
(I assume we've tried already?)

Do we want to fork wpa_supplicants' repo or keep the code in-tree?

wpa_supplicant is a fast moving project, so that definitely isn't ideal...
but as things stand fixing many, many bugs it has is a pain.

-- Alex

Other related posts: