14
I Use This!
Activity Not Available

News

Analyzed 2 months ago. based on code collected over 1 year ago.
Posted about 6 years ago by [email protected]
ffado-mixer.appdata.xml: Shorten screenshot caption. Jano Svitok informs us (via ffado-devel) that the screenshot captions in appdata files are apparently limited to 50 characters. This contradicts the advice given at ... [More] https://www.freedesktop.org/software/appstream/docs/chap-Quickstart.html which states the limit is 180. Oh well, if the limit is 50 that's what we have to run with. Thanks to Jano for the information. [Less]
Posted about 6 years ago by [email protected]
ffado-mixer.appdata.xml: add a screenshot. According to the appdata specification at least one screenshot must be supplied. This patch adds a URL to such a screenshot. A single screenshot will do for now: since the appearance varies ... [More] significantly depending on the audio interface in use there isn't a lot of point in providing too many detailed screenshots. [Less]
Posted about 6 years ago by [email protected]
ffado-mixer.appdata.xml: fix project licence identifier. While the table at http://spdx.org/licenses/ indicates that "GLP-2.0-only" is the appropriate tag for GPLv2 software, an alternative specification at ... [More] https://spdx.org/spdx-specification-21-web-version#h.1jlao46 says otherwise. The "appstream-util validate" command on Fedora reports "GPL-2.0-only" as invalid, so we'll run with "GPL-2.0" instead. Thanks to Orcan Ogetbil for running the appstream-util on his system and pointing out the URL with the alternative SPDX licence identifier definitions. [Less]
Posted about 6 years ago by [email protected]
Add support for a ffado-mixer.appdata.xml file. Distributions are starting to rely on appdata files to present applications in package management systems. Add an appdata file for ffado-mixer since this is the only significant component of FFADO ... [More] which counts as a user application. Thanks to Orcan Ogetbil for raising the issue on ffado-devel and providing an initial appdata file. For the moment this appdata file contains no screenshot, mostly because the screen content is dependent on the firewire interface in use at the time. We may revisit this in future if there's a call to do so. [Less]
Posted about 6 years ago by [email protected]
version.h: remove possible trailing dash from version number defines. Even after the changes in r2754, an unversioned source tree or a lack of svnversion on the build system will cause version.h to include entries like #define PACKAGE_VERSION ... [More] "2.4.999-" This patch from Orcan Ogetbil gets rid of the trailing dash. The use of REVISIONSTRING rather than REVISION mirrors how ffado-diag obtains its revision number. [Less]
Posted about 6 years ago by [email protected]
SConstruct: allow for unversioned source directory. When FFADO is compiled from a distribution archive the source tree is not under version control. This results in strings like libffado 2.4.0-Unversioned directory appearing in the ... [More] ffado-mixer "About" dialog box and ffado-diag. This problem was reported by Orcan Ogetbil on ffado-devel. Fix this by assuming that an unversioned directory is a release, thereby not requiring revision information in this case. An unversioned directory is detected by the appearance of "Unversioned" at the start of svnversion's output (as suggested by Orcan. Version information (which is determined separately) remains unchanged. A related corner case is when svnversion is not present on the build system. In this case the REVISION string will be empty (albeit with some pollution of stderr output to the terminal) so no additional action is required so long as an empty REVISION is considered acceptable. At this stage it seems fair: if svnversion (a component of subversion) is not present it's unlikely that the source tree has been checked out of svn. [Less]
Posted about 6 years ago by [email protected]
static_info.txt: install under LIBDIR/libffado/ rather than PYTHONDIR/. PYTHONDIR is usually located in a share hierarchy which (according to the fhs) should contain architecture-independent data. To address this, introduce the LIBDATADIR ... [More] directory (which defaults to LIBDIR/libffado/) and place static_info.txt there instead. Being under LIBDIR, architecture- dependent data can be placed there. Since information about libraries and paths is included in static_info.txt it clearly falls into the architecture-dependent category. Patch by Nicolas Boulenguez with minor changes by Jonathan Woithe. [Less]
Posted about 6 years ago by [email protected]
Remove support files obsoleted by r2751. These files were inadvertently left in place when r2751 was committed.
Posted about 6 years ago by [email protected]
Simplify and optimize ffado-diag.in. Executing ffado-diag after preprocessing ensures that the shebang python version is used without keeping SConscript in sync with ffado-diag.in. Merging all *.py modules into a single script will help any ... [More] contributor figuring the big picture, and spares the sys.path trick. The rewrite is more resilient to missing dependencies, and hopefully more readable. Patch contributed by Nicolas Boulenguez with minor adjustments by Jonathan Woithe. It has been tested under python3 and python2. [Less]
Posted about 6 years ago by [email protected]
Add comment explaining the "future" print_function imports. While Python 2.7 natively supports the print() function syntax of Python3, it is convenient to also make use of the "print(..., end=)" feature. This is not available under Python2 by ... [More] default, but can be accessed in Python2 by way of the "from future import print_function" statement. Include a brief comment to this effect in the relevant source files to make the purpose of the "future" import clear in future when the need for such lines might be deemed unnecessary. [Less]