summaryrefslogtreecommitdiff
path: root/configure.ac
AgeCommit message (Collapse)AuthorFilesLines
2016-11-07release: bump version to 1.14.41.14.4Aleksander Morgado1-1/+1
2016-04-03build: post release version bump to 1.14.3Aleksander Morgado1-1/+1
2016-04-03release: bump version to 1.14.21.14.2Aleksander Morgado1-3/+3
2016-03-17build: post release version bump to 1.14.1Aleksander Morgado1-1/+1
2016-03-17release: bump version to 1.14.01.14.0Aleksander Morgado1-4/+4
2016-01-30build: bump micro version to 1.13.7Aleksander Morgado1-1/+1
This is not an official release, just an easy way to identify when the new support for the UIM PIN actions was introduced.
2016-01-24build: bump micro version to 1.13.6Aleksander Morgado1-1/+1
This is not an official release, just an easy way to identify when the new support for the 'kernel expected data format' getter/setter were introduced.
2015-10-25nas: new optional TLV in 'Get Home Network' to know whether MNC is 2 or 3 digitsAleksander Morgado1-1/+1
Also, version bump to 1.13.5 to flag the exact version in which the change was introduced.
2015-02-07build: bump micro version to 1.13.4Aleksander Morgado1-1/+1
Not an official release, just a way to flag the availability of the new "DMS Set FCC Authentication" command.
2015-01-26nas: fix QMI_NAS_SIM_REJECT_STATE_SIM_AVAILABLE enum name (api break)Aleksander Morgado1-1/+1
Just a enum value rename, but breaks API. Also, version bump to 0.13.3 to flag the exact version in which the change was introduced.
2015-01-25nas: fix ECIO List TLV array element type (api break)Aleksander Morgado1-1/+1
ECIO List TLV (0x12) in the NAS Get Signal Strength response message is given as an unsigned byte, representing negative 0.5dB increments. This is an API break; added to NEWS already not to forget about it. Also, version bump to 0.13.2 to flag the exact version in which the change was introduced. https://bugs.freedesktop.org/show_bug.cgi?id=85052
2015-01-25nas: fix ECIO TLV field type (api break)Aleksander Morgado1-1/+1
ECIO TLV (0x14) in the NAS Event Report Indication message is given as an unsigned byte, representing negative 0.5dB increments. This is an API break; added to NEWS already not to forget about it. Also, version bump to 0.13.1 to flag the exact version in which the change was introduced. https://bugs.freedesktop.org/show_bug.cgi?id=85052
2015-01-13build: post release version bump to 1.13.0Aleksander Morgado1-1/+1
2015-01-13release: bump version to 1.12.01.12.0Aleksander Morgado1-4/+4
2015-01-09libqmi-glib,utils: avoid getpwnam() call if --enable-qmi-username not usedRoshan Pius1-6/+14
If --enable-qmi-username isn't explicitly used, we should just check for the root user UID, without using getpwnam(). See e.g. these SELinux warnings: SELinux is preventing /usr/bin/bash from read access on the file /etc/passwd. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that bash should be allowed read access on the passwd file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep qmi-proxy /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp
2014-12-19libqmi-glib,proxy: Change ownership of QMI devices to the configured user.Roshan Pius1-8/+25
Adding a udev rule to change ownership of all QMI devices to the configured user specified at compile time using --enable-qmi-username flag.
2014-11-18build: rename '--enable-qmi-proxy-username' to '--enable-qmi-username'Aleksander Morgado1-14/+10
This shouldn't be a proxy-only setting. We're going to chown the QMI devices to this specific user, so we'll re-use this setting for that as well.
2014-11-18libqmi-glib,proxy: add a configure flag to set the user ID of QMI proxyRoshan Pius1-0/+11
Currently, the QMI proxy process assumes that it is run as root user and that all incoming client connection users are also root. However, it's not always preferable to run the QMI proxy as root for security reasons. On some platforms, the QMI proxy could be constrained to run as a less-privileged user and specially granted the permission to access the QMI device. So, adding a compile time flag in libqmi to check for the specified user, rather than assume it to be the root user. If the flag is not sent, it'll revert to the existing behaviour of checking for user=root(i.e UID=0)
2014-09-05build: bump version to 1.11.1Aleksander Morgado1-1/+1
Not an official release, just a version bump to tag the availability of the new A-GPS related commands.
2014-05-29release: bump version to 1.11.0 (development)Aleksander Morgado1-1/+1
2014-05-29release: bump version to 1.10.01.10.0Aleksander Morgado1-3/+3
2013-12-11release: bump version to 1.9.0 (development)Aleksander Morgado1-1/+1
2013-12-11release: bump version to 1.8.01.8.0Aleksander Morgado1-3/+3
2013-09-05qmi-proxy: initial implementationAleksander Morgado1-0/+1
2013-09-05libqmi-glib,device: use gio i/o streams instead of glib i/o channelsAleksander Morgado1-1/+2
2013-09-05build: consolidate the glib requirementsAleksander Morgado1-12/+4
Don't split requirements per product built, but per actual requirement.
2013-09-05build: move source code under src/Aleksander Morgado1-6/+7
2013-09-05release: bump version to 1.7.0 (development)Aleksander Morgado1-1/+1
2013-09-05release: bump version to 1.6.01.6.0Aleksander Morgado1-2/+2
2013-09-04build: Make help2man optionalColin Walters1-0/+1
I don't have it in gnome-ostree, nor at the moment man page stuff in general.
2013-09-04man: generate qmicli manpage from --help-allAleksander Morgado1-1/+5
2013-06-21build: setup gtester based unit testsAleksander Morgado1-13/+0
2013-06-13build: setup libtool versioning for libqmi-glibAleksander Morgado1-0/+21
Let it be 0.0.0 for now; we have not updated this in the past versions, but we should do it from now on.
2013-06-13libqmi-glib,api: provide version infoAleksander Morgado1-1/+19
2013-06-07release: bump version to 1.5.0 (development)Dan Williams1-1/+1
2013-06-07release: bump version to 1.4.01.4.0Dan Williams1-1/+1
2013-05-06docs: always generate docs at dist timeYanko Kaneti1-11/+1
The pregenerated docs will be in the dist tarball, and will even be installed with 'make install' when building the dist tarball.
2013-03-20release: bump version to 1.3.0 (development)Dan Williams1-1/+1
2013-03-19release: bump version to 1.2.01.2.0Dan Williams1-1/+1
2012-11-12release: bump version to 1.0.01.0.0Dan Williams1-1/+1
2012-10-09libqmi-glib: message traces compiled alwaysAleksander Morgado1-11/+0
Message traces have been very useful when debugging issues in the protocol, and we should avoid requiring a full recompilation in order to get them enabled. Instead, we provide two new API methods, `qmi_utils_(get|set)_traces_enabled()', which allow specifying whether traces should be dumped with g_debug() or not.
2012-10-09build: compile all generated code into a non-installable libraryAleksander Morgado1-0/+1
Also simplify the build by using BUILT_SOURCES to avoid needing to specify custom dependency rules.
2012-09-24use $PKG_CONFIGMike Frysinger1-1/+1
The build system sets up this variable for us, so use it rather than hardcoding "pkg-config" which might be the wrong one. Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2012-08-28build: minor indentation fixesAleksander Morgado1-4/+4
2012-08-22build: add --with-traces=yes to enable -DMESSAGE_ENABLE_TRACEDan Williams1-0/+11
2012-08-03docs: setup initial gtk-doc documentationAleksander Morgado1-1/+19
2012-07-16cli: new helper method to get raw binary data as a printable stringAleksander Morgado1-0/+1
2012-07-04libqmi-glib,test: new unit tests for the integer read/write operationsAleksander Morgado1-0/+14
2012-07-03build: prepare sources to treat `libqmi-glib' not as the only libraryAleksander Morgado1-6/+6
Instead of keeping the libqmi-glib sources under `src', we'll have a more specific `libqmi-glib' directory instead. Also, update autotools to reflect as `libqmi' the name of the project.
2012-07-03qmi-codegen: use `g_array_set_clear_func()' to clear array contentsAleksander Morgado1-1/+1
Bumped required glib version to 2.32. Actually... there is no real issue with keeping 2.28 as minimum required version, as for now there's no array element which requires clearing, but anyway, given that QMI is to be used in quite recent kernels, it shouldn't be a big issue to require a recent glib as well.