[hfreyther: We assume that the user might install OpenVPN with
a different priority but that it will always be available in the
runlevel two (e.g. even if the user changed the default runlevel)]
Related: SYS#517
I have no idea who creates the /run/openvpn directory on Debian.
The path is not in a tmpfiles.d and I don't see the generator
creating it or the service file indicating that it needs to be
created. Place the file with openvpn.NAME.status into the /run
directory which appears to work on the device.
We want to use systemd for managing the lifetime of OpenVPN. Take
the debian generator (which should work with busybox ash) and the
openvpn.service (to inhibit the sysvinit script) and the target
file and install it.
On systems that have ran "update-rc.d openvpn defaults" one need
to manually execute a systemctl enable openvpn.service. This is
not done through a post-inst script and I am not sure if we should
do it. This means there is a danger of ending with a unit that
doesn't start OpenVPN automatically after upgrade!
The scripts/packages have not been tested on a device yet.
We should use a more recent version of the OpenVPN client. Import
it from the meta-networking layer like we did before. The sysvinit
script has just minor whitespace differences and wasn't imported.
We need to test opkg upgrades of OpenVPN through the VPN. We don't
want to kill the tunnel on such upgrade.
In dora there is no autotools-brokensep bbclass. So let's just
set the build directory to the source directory ourselves. I have
not built the package for dora though/
Poky dizzy is more strict with -I/usr/include and the old
tcpdump could pick-up "/usr/bin/pcap-config" from the host
and fail. Just upgrade to a newer version of tcpdump and be
done with it.
We want to have a single image that will do the right thing on
the various BTS models we have. This means we will install the
sbts2050 utilitiy (it clashes with sysmobts-mgr anyway) and the
gpsd with a default config for it.
The sysmobts-v2 config file was for a specific usecase and is
obsolete for all intents and purposes. Make it the default
Related: SYS#559
Enabling the "systemd" feature will enable the socket activation
feature used by systemd. This way we can (re-)start the GPSD based
on the socket activation.
Henning got really confused that the "a.b.c:1234" he passed to
gps2udp showed up as "a.b.c 1234" in the kernel cmdline. Use
strdup to take a copy of it.
Fixes: SYS#424
So far we have used chrpath to fix the rpath we don't want but
this creates issues with supporting both dora and edison (we need
to depend on different recipes). Instead just force the RPATH to
be off. This can be done by setting the internal _RPATH variable.
I found this in Tool/gnulink.py.
The .pc files were already covered by the normal -dev package
glob. No need to do more work here.
Addresses:
WARNING: Variable key FILES_${PN}-dev (${includedir} ${FILES_SOLIBSDEV} ${libdir}/*.la ${libdir}/*.o ${libdir}/pkgconfig ${datadir}/pkgconfig ${datadir}/aclocal ${base_libdir}/*.o ${libdir}/${BPN}/*.la ${base_libdir}/*.la) replaces original key FILES_gpsd-dev ( ${libdir}/pkgconfdir/libgpsd.pc ${libdir}/pkgconfdir/libgps.pc).
In the sysmoBTS 2050, we want to configure the 1PPS output of the
trimble to be active only if it has at least 1 satellite in view,
and want to make the receiver output its time information in UTC,
rather than GPS time.
The sysmobts-v2 version was not installed because the file was
not called properly. Rename it to gpsd-default and the sysmobts-v2
version will be picked and installed.
GPSD 3.7 is somehow exiting without us really knowing the cause. The
version 3.9 has been released and we hope that it might just fix the
issues we are experiencing.
Ask the buildsystem to install the manpages to the mandir. This will avoid
the following warning.
WARNING: QA Issue: lmsensors-apps: Files/directories were installed but not shipped
/usr/man
RROR: There is a confusing multiline, partially commented expression on line 22 of file /home/ich/firmen/gesmokom/source/meta-sysmocom-bsp/recipes-extra/gpsd/gpsd_3.7.bb (SRC_URI[md5sum] = "52d9785eaf1a51298bb8900dbde88f98").
We could use "fakeroot do_install() {}" but this will still not
make the spool directory be owned by uucp. Use a postinst script
to make this up. The logic is copied from the cronie bitbake file
and we will see how this works at image creation time.
FIXME: this will actually assume a GPS that is indirectly attached
to a GSM Modem which will be handled by openmoko-gsmd and forwarded via
UDP. However, we might have a GPS receiver attached directly to the
GPS UART in other hardware versions!
The idea is that the basic extension resides inside the the normal
recipe directories. Depending on the version of poky the bbappends
need to be included. Appends applying to all versions will be put
into the shared folder, specific ones into the specific directory.
Once a bbappend can not be shared anymore it needs to be copied.
First ca-certificates does not create a symlink from /etc/ssl/certs
to /usr/lib/ssl/certs, second it does not run the c_rehash perl utility
making the recipe pretty useless and third it trusts way too many
cert authorities.
socat is useful for the self-hosted-image work.
The original recipe is from OE:
http://git.openembedded.org/openembedded/tree/recipes/socat/
and I upgraded it to 1.7.2.0.
Thank Koen Kooi <koen@dominion.thruhere.net> for suggesting
how to assign the LICENSE field with a proper value.
(From OE-Core rev: b1771ff0ad39250678bd53b0ae7543c9365572f5)
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>