osmo-{bts,pcu}: Fix systemd services to run against old systemd
recipes/sysmobts/osmo-{bts,pcu}: build from tag
b1bd3ca685
openvpn: upgrade openvpn from 2.3.6 to 2.5.8
37f85b45a8
gpsdate: upgrade to fix build against new gpsd
ca6fbf6a9f
gpsd: upgrade to 3.24
ae9efed470
gpsd: cosmetic fixes in SRC_URI, EXTRA_OESCONS
6bd713e77a
set up osmocom recipes with AUTOREV to track git master
3fc844e59a
osmo-bts: Depend on libosmo-netif
9a554791fe
Update Osmocom recipes to latest tags (release 202302)
3fc844e59a
osmo-bts: Depend on libosmo-netif
9a554791fe
Update Osmocom recipes to latest tags (release 202302)
Fix build against gpsd >= 3.20
For this gps_read() function since we always call it with one "variable" param in then, the best is to do a shim. I recall doing that somewhere already in gpsdata or gpsd in the past, look around. Something like:
gpsd: upgrade to 3.24
My point is precisely that the submitted commits should be made from the point of view of: 1- importing a given well-known upstream recipe from poky/meta-* and providing info about the repo and…
Fix build against gpsd >= 3.20
I'd rather keep supporting older versions by means of ifdef in relevant code parts, or having a function helper defined for different versions. IIRC we are already doing that in some places?