AUTHORS

+Landry Breuil <landry at rhaalovely.net>

COPYING

+Copyright (c) 2006 Landry Breuil (landry at fr.homeunix.org / gaston at gcu.info)
+This code is licenced under a BSD-style licence. 
+(OpenBSD variant modeled after the ISC licence)
+All rights reserved.
+Permission to use, copy, modify, and distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

ChangeLog

+08-12-2018 Landry Breuil <landry at xfce.org>
+   * release 0.5.1
+   * fix a long-standing crasher when using multiple outputs
+   * improve icon sizing on 4.13 panel (thx to Simon Steinbeiss)
+   * improve spacing in settings dialog (#14671, thx to Sean Davis)
+   * allow %file% in format_song_display (#12973, thx to Armando Ortega)
+
+01-11-2016 Landry Breuil <landry at xfce.org>
+   * release 0.5.0
+   * fix changing volume via mousewheel
+   * fix icon flickering on mousehover
+   * properly resize button/image on set_size event
+
+05-06-2016 Landry Breuil <landry at xfce.org>
+   * release 0.4.99
+   * port to gtk+3/libxfce4ui-2/libxfce4panel-2.0
+
+04-03-2015 Landry Breuil <landry at xfce.org>
+   * release 0.4.5
+   * autotools update
+   * new translations: bg, en_AU, ms, nb, oc, th, sr
+   * updated translations: ar, ast, cs, da, de, en_AU, es, fr, he
+     hr, hu, id, ko, nl, pl, sk, sv, tr, ru, ug, uk, zh_CN, zh_TW
+
+30-06-2012 Landry Breuil <landry at xfce.org>
+   * release 0.4.4
+   * Better compliance with the panel plugin HIG
+   * Fix wrong fr translation
+
+13-05-2012 Landry Breuil <landry at xfce.org>
+   * release 0.4.3
+   * set small property (unless in deskbar mode)
+   * fix panel 4.9 detection
+
+20-02-2012 Landry Breuil <landry at rhaalovely.net>
+   * release 0.4.2
+   * 0.4.1 was generated with a buggy intltool 0.50.0, regen with 0.50.1
+   * https://bugs.launchpad.net/intltool/+bug/900738
+
+15-02-2012 Landry Breuil <landry at rhaalovely.net>
+   * release 0.4.1
+   * build plugin as a module
+   * add nrows handling/mode-changed callback for panel > 4.9
+
+12-02-2012 Landry Breuil <landry at rhaalovely.net>
+   * release 0.4.0
+   * port from libxfcegui4 to libxfce4ui
+   * much better handling of panel size/orientation
+   * use icon names from the icon-naming-specs
+   * looks much better and obey panel/icon themes
+   * make plugin background transparent
+
+07-01-2011 Landry Breuil <landry at rhaalovely.net>
+   * release 0.3.6
+   * recognize exo-1 for upcoming Xfce 4.8
+
+17-05-2010 Landry Breuil <landry at fr.homeunix.org>
+   * release 0.3.5
+   * add enable/disable outputs in rightclick menu
+
+03-11-2009 Landry Breuil <landry at fr.homeunix.org>
+   * release 0.3.4
+   * add user-configurable markup for playlist and tooltip
+   * properly resize buttons icons
+
+24-03-2008 Landry Breuil <landry at fr.homeunix.org>
+   * release 0.3.3
+   * pretty-print tracks in playlist and tooltip
+   * don't show multiple instances of playlist
+   * fix dumb segfaults when connection is dropped by MPD
+   * add aboutbox (useless, hence necessary)
+
+30-05-2007 Landry Breuil <landry at fr.homeunix.org>
+   * release 0.3.2
+   * fixed various bugs when running against MPD 0.12.2 or 0.13 (thanks drac)
+   * fixed stupid bug, first track was not shown in playlist
+   * rewritten parser in simple-libmpd.c using g_* funcs
+
+28-01-2007 Landry Breuil <landry at fr.homeunix.org>
+   * release 0.3.1
+   * fixed bugs in simple-libmpd.c, causing several crashes
+   * prevent creation of playlist window when mpd could not be contacted
+
+16-01-2007 Landry Breuil <landry at fr.homeunix.org>
+   * release 0.3.0
+   * added configurable client (gmpc, xterm -e ncmpc,..) entry in context menu (uses xfce_exec())
+   * added simple playlist window on middle-click permitting to select a track to play
+   * completed simple-libmpd to improve communication with mpd
+
+26-10-2006 Landry Breuil <landry at fr.homeunix.org>
+   * release 0.2.0
+   * written a simple interface with mpd when libmpd is not available
+   * cleaned/modularized code
+   * add repeat/random toggle in right-click menu
+   * use xfce_* functions for config dialog
+   * replaced play call/button with pause -> better
+   * don't connect at startup (plugin is not configured)
+
+11-06-2006 Landry Breuil <landry at fr.homeunix.org>
+   * Initial release 0.1.0
+   * depends on libmpd
+   * Features : 
+   * prev/next/stop/play buttons with gtk stock icons
+   * mousewheel to increase/decrease volume
+   * current title as tooltip
+   * configurable MPD host/port/password

INSTALL

+Installation Instructions
+*************************
+
+Copyright (C) 1994-1996, 1999-2002, 2004-2013 Free Software Foundation,
+Inc.
+
+   Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved.  This file is offered as-is,
+without warranty of any kind.
+
+Basic Installation
+==================
+
+   Briefly, the shell command `./configure && make && make install'
+should configure, build, and install this package.  The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package.  Some packages provide this
+`INSTALL' file but do not implement all of the features documented
+below.  The lack of an optional feature in a given package is not
+necessarily a bug.  More recommendations for GNU packages can be found
+in *note Makefile Conventions: (standards)Makefile Conventions.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+   It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring.  Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+   The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'.  You need `configure.ac' if
+you want to change it or regenerate `configure' using a newer version
+of `autoconf'.
+
+   The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.
+
+     Running `configure' might take a while.  While running, it prints
+     some messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package, generally using the just-built uninstalled binaries.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.  When installing into a prefix owned by root, it is
+     recommended that the package be configured and built as a regular
+     user, and only the `make install' phase executed with root
+     privileges.
+
+  5. Optionally, type `make installcheck' to repeat any self-tests, but
+     this time using the binaries in their final installed location.
+     This target does not install anything.  Running this target as a
+     regular user, particularly if the prior `make install' required
+     root privileges, verifies that the installation completed
+     correctly.
+
+  6. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+  7. Often, you can also type `make uninstall' to remove the installed
+     files again.  In practice, not all packages have tested that
+     uninstallation works correctly, even though it is required by the
+     GNU Coding Standards.
+
+  8. Some packages, particularly those that use Automake, provide `make
+     distcheck', which can by used by developers to test that all other
+     targets like `make install' and `make uninstall' work correctly.
+     This target is generally not run by end users.
+
+Compilers and Options
+=====================
+
+   Some systems require unusual options for compilation or linking that
+the `configure' script does not know about.  Run `./configure --help'
+for details on some of the pertinent environment variables.
+
+   You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment.  Here
+is an example:
+
+     ./configure CC=c99 CFLAGS=-g LIBS=-lposix
+
+   *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+   You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory.  To do this, you can use GNU `make'.  `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script.  `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.  This
+is known as a "VPATH" build.
+
+   With a non-GNU `make', it is safer to compile the package for one
+architecture at a time in the source code directory.  After you have
+installed the package for one architecture, use `make distclean' before
+reconfiguring for another architecture.
+
+   On MacOS X 10.5 and later systems, you can create libraries and
+executables that work on multiple system types--known as "fat" or
+"universal" binaries--by specifying multiple `-arch' options to the
+compiler but only a single `-arch' option to the preprocessor.  Like
+this:
+
+     ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+                 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+                 CPP="gcc -E" CXXCPP="g++ -E"
+
+   This is not guaranteed to produce working output in all cases, you
+may have to build one architecture at a time and combine the results
+using the `lipo' tool if you have problems.
+
+Installation Names
+==================
+
+   By default, `make install' installs the package's commands under
+`/usr/local/bin', include files under `/usr/local/include', etc.  You
+can specify an installation prefix other than `/usr/local' by giving
+`configure' the option `--prefix=PREFIX', where PREFIX must be an
+absolute file name.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
+
+   In addition, if you use an unusual directory layout you can give
+options like `--bindir=DIR' to specify different values for particular
+kinds of files.  Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.  In general, the
+default for these options is expressed in terms of `${prefix}', so that
+specifying just `--prefix' will affect all of the other directory
+specifications that were not explicitly provided.
+
+   The most portable way to affect installation locations is to pass the
+correct locations to `configure'; however, many packages provide one or
+both of the following shortcuts of passing variable assignments to the
+`make install' command line to change installation locations without
+having to reconfigure or recompile.
+
+   The first method involves providing an override variable for each
+affected directory.  For example, `make install
+prefix=/alternate/directory' will choose an alternate location for all
+directory configuration variables that were expressed in terms of
+`${prefix}'.  Any directories that were specified during `configure',
+but not in terms of `${prefix}', must each be overridden at install
+time for the entire installation to be relocated.  The approach of
+makefile variable overrides for each directory variable is required by
+the GNU Coding Standards, and ideally causes no recompilation.
+However, some platforms have known limitations with the semantics of
+shared libraries that end up requiring recompilation when using this
+method, particularly noticeable in packages that use GNU Libtool.
+
+   The second method involves providing the `DESTDIR' variable.  For
+example, `make install DESTDIR=/alternate/directory' will prepend
+`/alternate/directory' before all installation names.  The approach of
+`DESTDIR' overrides is not required by the GNU Coding Standards, and
+does not work on platforms that have drive letters.  On the other hand,
+it does better at avoiding recompilation issues, and works well even
+when some directory options were not specified in terms of `${prefix}'
+at `configure' time.
+
+Optional Features
+=================
+
+   If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+   Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System).  The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+   For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+   Some packages offer the ability to configure how verbose the
+execution of `make' will be.  For these packages, running `./configure
+--enable-silent-rules' sets the default to minimal output, which can be
+overridden with `make V=1'; while running `./configure
+--disable-silent-rules' sets the default to verbose, which can be
+overridden with `make V=0'.
+
+Particular systems
+==================
+
+   On HP-UX, the default C compiler is not ANSI C compatible.  If GNU
+CC is not installed, it is recommended to use the following options in
+order to use an ANSI C compiler:
+
+     ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
+
+and if that doesn't work, install pre-built binaries of GCC for HP-UX.
+
+   HP-UX `make' updates targets which have the same time stamps as
+their prerequisites, which makes it generally unusable when shipped
+generated files such as `configure' are involved.  Use GNU `make'
+instead.
+
+   On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
+parse its `<wchar.h>' header file.  The option `-nodtk' can be used as
+a workaround.  If GNU CC is not installed, it is therefore recommended
+to try
+
+     ./configure CC="cc"
+
+and if that doesn't work, try
+
+     ./configure CC="cc -nodtk"
+
+   On Solaris, don't put `/usr/ucb' early in your `PATH'.  This
+directory contains several dysfunctional programs; working variants of
+these programs are available in `/usr/bin'.  So, if you need `/usr/ucb'
+in your `PATH', put it _after_ `/usr/bin'.
+
+   On Haiku, software installed for all users goes in `/boot/common',
+not `/usr/local'.  It is recommended to use the following options:
+
+     ./configure --prefix=/boot/common
+
+Specifying the System Type
+==========================
+
+   There may be some features `configure' cannot figure out
+automatically, but needs to determine by the type of machine the package
+will run on.  Usually, assuming the package is built to be run on the
+_same_ architectures, `configure' can figure that out, but if it prints
+a message saying it cannot guess the machine type, give it the
+`--build=TYPE' option.  TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+     CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+     OS
+     KERNEL-OS
+
+   See the file `config.sub' for the possible values of each field.  If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+   If you are _building_ compiler tools for cross-compiling, you should
+use the option `--target=TYPE' to select the type of system they will
+produce code for.
+
+   If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+Sharing Defaults
+================
+
+   If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `config.site' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists.  Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+   Variables not defined in a site shell script can be set in the
+environment passed to `configure'.  However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost.  In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'.  For example:
+
+     ./configure CC=/usr/local2/bin/gcc
+
+causes the specified `gcc' to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
+an Autoconf limitation.  Until the limitation is lifted, you can use
+this workaround:
+
+     CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+`configure' Invocation
+======================
+
+   `configure' recognizes the following options to control how it
+operates.
+
+`--help'
+`-h'
+     Print a summary of all of the options to `configure', and exit.
+
+`--help=short'
+`--help=recursive'
+     Print a summary of the options unique to this package's
+     `configure', and exit.  The `short' variant lists options used
+     only in the top level, while the `recursive' variant lists options
+     also present in any nested packages.
+
+`--version'
+`-V'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`--cache-file=FILE'
+     Enable the cache: use and save the results of the tests in FILE,
+     traditionally `config.cache'.  FILE defaults to `/dev/null' to
+     disable caching.
+
+`--config-cache'
+`-C'
+     Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to `/dev/null' (any error
+     messages will still be shown).
+
+`--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     `configure' can determine that directory automatically.
+
+`--prefix=DIR'
+     Use DIR as the installation prefix.  *note Installation Names::
+     for more details, including other options available for fine-tuning
+     the installation locations.
+
+`--no-create'
+`-n'
+     Run the configure checks, but stop before creating any output
+     files.
+
+`configure' also accepts some other, not widely useful, options.  Run
+`configure --help' for more details.

Makefile.am

+@SET_MAKE@
+
+SUBDIRS = panel-plugin po
+
+distclean-local:
+	rm -rf *.cache *~
+
+EXTRA_DIST = 								\
+	README								\
+	intltool-extract.in						\
+	intltool-merge.in						\
+	intltool-update.in
+
+DISTCLEANFILES =							\
+	intltool-extract						\
+	intltool-merge							\
+	intltool-update
+

README

+Xfce4-Mpc-Plugin
+----------------
+
+This is a simple Musicpd (http://www.musicpd.org) client plugin for the Xfce panel.
+Features :
+- next/stop/play/pause/previous buttons
+- current volume/status/playing track when mouse passes over the plugin
+- decrease/increase volume with mousewheel
+- show a simple playlist window upon middle-click, permitting to select a track to play
+- toggle random/repeat/outputs in right-click menu
+- launch configurable client (gmpc, xterm -e ncmpc,..) through right-click menu
+- configurable tooltip and playlist formats, using a gmpc-like markup :
+  - playlist accepts %artist%, %title%, %album% and %track%
+  - tooltip accepts the same plus %vol%, %status% and %newline%
+
+To build it, you have two options :
+- against libmpd libraries :
+Get'em from your OS' repository/ports, or from source
+It will be autodetected by pkg-config.
+If libmpd is not installed in a standard directory, use --with-libmpd=path_to_libmpd.
+- without libmpd, using simple-libmpd :
+Since 0.2.0, i implemented a simple interface with mpd, using plain old sockets.
+If libmpd is not found, it will be used as a fallback (or if you specify --without-libmpd)
+
+./configure && make && su -c make install should suffice in most cases.
+
+If it crashes, recompile it with --enable-debug=full, add it to the panel, attach gdb to it
+(gdb -p `pgrep -f libmpc` , continue) and report a bug with a complete backtrace.
+
+This little piece of code is licensed under a BSD-style licence.
+(OpenBSD variant modeled after the ISC licence)

TODO

+- add volume progressbar/slider ?
+- fix all strings length checking
+- adapt to panel 4.10 w/ nrows/deskbar-mode

compile

+#! /bin/sh
+# Wrapper for compilers which do not understand '-c -o'.
+
+scriptversion=2012-10-14.11; # UTC
+
+# Copyright (C) 1999-2013 Free Software Foundation, Inc.
+# Written by Tom Tromey <tromey@cygnus.com>.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+# As a special exception to the GNU General Public License, if you
+# distribute this file as part of a program that contains a
+# configuration script generated by Autoconf, you may include it under
+# the same distribution terms that you use for the rest of that program.
+
+# This file is maintained in Automake, please report
+# bugs to <bug-automake@gnu.org> or send patches to
+# <automake-patches@gnu.org>.
+
+nl='
+'
+
+# We need space, tab and new line, in precisely that order.  Quoting is
+# there to prevent tools from complaining about whitespace usage.
+IFS=" ""	$nl"
+
+file_conv=
+
+# func_file_conv build_file lazy
+# Convert a $build file to $host form and store it in $file
+# Currently only supports Windows hosts. If the determined conversion
+# type is listed in (the comma separated) LAZY, no conversion will
+# take place.
+func_file_conv ()
+{
+  file=$1
+  case $file in
+    / | /[!/]*) # absolute file, and not a UNC file
+      if test -z "$file_conv"; then
+	# lazily determine how to convert abs files
+	case `uname -s` in
+	  MINGW*)
+	    file_conv=mingw
+	    ;;
+	  CYGWIN*)
+	    file_conv=cygwin
+	    ;;
+	  *)
+	    file_conv=wine
+	    ;;
+	esac
+      fi
+      case $file_conv/,$2, in
+	*,$file_conv,*)
+	  ;;
+	mingw/*)
+	  file=`cmd //C echo "$file " | sed -e 's/"\(.*\) " *$/\1/'`
+	  ;;
+	cygwin/*)
+	  file=`cygpath -m "$file" || echo "$file"`
+	  ;;
+	wine/*)
+	  file=`winepath -w "$file" || echo "$file"`
+	  ;;
+      esac
+      ;;
+  esac
+}
+
+# func_cl_dashL linkdir
+# Make cl look for libraries in LINKDIR
+func_cl_dashL ()
+{
+  func_file_conv "$1"
+  if test -z "$lib_path"; then
+    lib_path=$file
+  else
+    lib_path="$lib_path;$file"
+  fi
+  linker_opts="$linker_opts -LIBPATH:$file"
+}
+
+# func_cl_dashl library
+# Do a library search-path lookup for cl
+func_cl_dashl ()
+{
+  lib=$1
+  found=no
+  save_IFS=$IFS
+  IFS=';'
+  for dir in $lib_path $LIB
+  do
+    IFS=$save_IFS
+    if $shared && test -f "$dir/$lib.dll.lib"; then
+      found=yes
+      lib=$dir/$lib.dll.lib
+      break
+    fi
+    if test -f "$dir/$lib.lib"; then
+      found=yes
+      lib=$dir/$lib.lib
+      break
+    fi
+    if test -f "$dir/lib$lib.a"; then
+      found=yes
+      lib=$dir/lib$lib.a
+      break
+    fi
+  done
+  IFS=$save_IFS
+
+  if test "$found" != yes; then
+    lib=$lib.lib
+  fi
+}
+
+# func_cl_wrapper cl arg...
+# Adjust compile command to suit cl
+func_cl_wrapper ()
+{
+  # Assume a capable shell
+  lib_path=
+  shared=:
+  linker_opts=
+  for arg
+  do
+    if test -n "$eat"; then
+      eat=
+    else
+      case $1 in
+	-o)
+	  # configure might choose to run compile as 'compile cc -o foo foo.c'.
+	  eat=1
+	  case $2 in
+	    *.o | *.[oO][bB][jJ])
+	      func_file_conv "$2"
+	      set x "$@" -Fo"$file"
+	      shift
+	      ;;
+	    *)
+	      func_file_conv "$2"
+	      set x "$@" -Fe"$file"
+	      shift
+	      ;;
+	  esac
+	  ;;
+	-I)
+	  eat=1
+	  func_file_conv "$2" mingw
+	  set x "$@" -I"$file"
+	  shift
+	  ;;
+	-I*)
+	  func_file_conv "${1#-I}" mingw
+	  set x "$@" -I"$file"
+	  shift
+	  ;;
+	-l)
+	  eat=1
+	  func_cl_dashl "$2"
+	  set x "$@" "$lib"
+	  shift
+	  ;;
+	-l*)
+	  func_cl_dashl "${1#-l}"
+	  set x "$@" "$lib"
+	  shift
+	  ;;
+	-L)
+	  eat=1
+	  func_cl_dashL "$2"
+	  ;;
+	-L*)
+	  func_cl_dashL "${1#-L}"
+	  ;;
+	-static)
+	  shared=false
+	  ;;
+	-Wl,*)
+	  arg=${1#-Wl,}
+	  save_ifs="$IFS"; IFS=','
+	  for flag in $arg; do
+	    IFS="$save_ifs"
+	    linker_opts="$linker_opts $flag"
+	  done
+	  IFS="$save_ifs"
+	  ;;
+	-Xlinker)
+	  eat=1
+	  linker_opts="$linker_opts $2"
+	  ;;
+	-*)
+	  set x "$@" "$1"
+	  shift
+	  ;;
+	*.cc | *.CC | *.cxx | *.CXX | *.[cC]++)
+	  func_file_conv "$1"
+	  set x "$@" -Tp"$file"
+	  shift
+	  ;;
+	*.c | *.cpp | *.CPP | *.lib | *.LIB | *.Lib | *.OBJ | *.obj | *.[oO])
+	  func_file_conv "$1" mingw
+	  set x "$@" "$file"
+	  shift
+	  ;;
+	*)
+	  set x "$@" "$1"
+	  shift
+	  ;;
+      esac
+    fi
+    shift
+  done
+  if test -n "$linker_opts"; then
+    linker_opts="-link$linker_opts"
+  fi
+  exec "$@" $linker_opts
+  exit 1
+}
+
+eat=
+
+case $1 in
+  '')
+     echo "$0: No command.  Try '$0 --help' for more information." 1>&2
+     exit 1;
+     ;;
+  -h | --h*)
+    cat <<\EOF
+Usage: compile [--help] [--version] PROGRAM [ARGS]
+
+Wrapper for compilers which do not understand '-c -o'.
+Remove '-o dest.o' from ARGS, run PROGRAM with the remaining
+arguments, and rename the output as expected.
+
+If you are trying to build a whole package this is not the
+right script to run: please start by reading the file 'INSTALL'.
+
+Report bugs to <bug-automake@gnu.org>.
+EOF
+    exit $?
+    ;;
+  -v | --v*)
+    echo "compile $scriptversion"
+    exit $?
+    ;;
+  cl | *[/\\]cl | cl.exe | *[/\\]cl.exe )
+    func_cl_wrapper "$@"      # Doesn't return...
+    ;;
+esac
+
+ofile=
+cfile=
+
+for arg
+do
+  if test -n "$eat"; then
+    eat=
+  else
+    case $1 in
+      -o)
+	# configure might choose to run compile as 'compile cc -o foo foo.c'.
+	# So we strip '-o arg' only if arg is an object.
+	eat=1
+	case $2 in
+	  *.o | *.obj)
+	    ofile=$2
+	    ;;
+	  *)
+	    set x "$@" -o "$2"
+	    shift
+	    ;;
+	esac
+	;;
+      *.c)
+	cfile=$1
+	set x "$@" "$1"
+	shift
+	;;
+      *)
+	set x "$@" "$1"
+	shift
+	;;
+    esac
+  fi
+  shift
+done
+
+if test -z "$ofile" || test -z "$cfile"; then
+  # If no '-o' option was seen then we might have been invoked from a
+  # pattern rule where we don't need one.  That is ok -- this is a
+  # normal compilation that the losing compiler can handle.  If no
+  # '.c' file was seen then we are probably linking.  That is also
+  # ok.
+  exec "$@"
+fi
+
+# Name of file we expect compiler to create.
+cofile=`echo "$cfile" | sed 's|^.*[\\/]||; s|^[a-zA-Z]:||; s/\.c$/.o/'`
+
+# Create the lock directory.
+# Note: use '[/\\:.-]' here to ensure that we don't use the same name
+# that we are using for the .o file.  Also, base the name on the expected
+# object file name, since that is what matters with a parallel build.
+lockdir=`echo "$cofile" | sed -e 's|[/\\:.-]|_|g'`.d
+while true; do
+  if mkdir "$lockdir" >/dev/null 2>&1; then
+    break
+  fi
+  sleep 1
+done
+# FIXME: race condition here if user kills between mkdir and trap.
+trap "rmdir '$lockdir'; exit 1" 1 2 15
+
+# Run the compile.
+"$@"
+ret=$?
+
+if test -f "$cofile"; then
+  test "$cofile" = "$ofile" || mv "$cofile" "$ofile"
+elif test -f "${cofile}bj"; then
+  test "${cofile}bj" = "$ofile" || mv "${cofile}bj" "$ofile"
+fi
+
+rmdir "$lockdir"
+exit $ret
+
+# Local Variables:
+# mode: shell-script
+# sh-indentation: 2
+# eval: (add-hook 'write-file-hooks 'time-stamp)
+# time-stamp-start: "scriptversion="
+# time-stamp-format: "%:y-%02m-%02d.%02H"
+# time-stamp-time-zone: "UTC"
+# time-stamp-end: "; # UTC"
+# End:

config.h.in

+/* config.h.in.  Generated from configure.ac by autoheader.  */
+
+/* Define for debugging support */
+#undef DEBUG
+
+/* Define for tracing support */
+#undef DEBUG_TRACE
+
+/* always defined to indicate that i18n is enabled */
+#undef ENABLE_NLS
+
+/* Name of default gettext domain */
+#undef GETTEXT_PACKAGE
+
+/* Define to 1 if you have the `bind_textdomain_codeset' function. */
+#undef HAVE_BIND_TEXTDOMAIN_CODESET
+
+/* Define to 1 if you have the Mac OS X function CFLocaleCopyCurrent in the
+   CoreFoundation framework. */
+#undef HAVE_CFLOCALECOPYCURRENT
+
+/* Define to 1 if you have the Mac OS X function CFPreferencesCopyAppValue in
+   the CoreFoundation framework. */
+#undef HAVE_CFPREFERENCESCOPYAPPVALUE
+
+/* Define to 1 if you have the `dcgettext' function. */
+#undef HAVE_DCGETTEXT
+
+/* Define to 1 if you have the <dlfcn.h> header file. */
+#undef HAVE_DLFCN_H
+
+/* Define if the GNU gettext() function is already present or preinstalled. */
+#undef HAVE_GETTEXT
+
+/* Define to 1 if you have the <inttypes.h> header file. */
+#undef HAVE_INTTYPES_H
+
+/* Define if your <locale.h> file defines LC_MESSAGES. */
+#undef HAVE_LC_MESSAGES
+
+/* libmpd found */
+#undef HAVE_LIBMPD
+
+/* Define to 1 if you have the <locale.h> header file. */
+#undef HAVE_LOCALE_H
+
+/* Define to 1 if you have the <memory.h> header file. */
+#undef HAVE_MEMORY_H
+
+/* Define to 1 if you have the <stdint.h> header file. */
+#undef HAVE_STDINT_H
+
+/* Define to 1 if you have the <stdlib.h> header file. */
+#undef HAVE_STDLIB_H
+
+/* Define to 1 if you have the <strings.h> header file. */
+#undef HAVE_STRINGS_H
+
+/* Define to 1 if you have the <string.h> header file. */
+#undef HAVE_STRING_H
+
+/* Define to 1 if you have the <sys/stat.h> header file. */
+#undef HAVE_SYS_STAT_H
+
+/* Define to 1 if you have the <sys/types.h> header file. */
+#undef HAVE_SYS_TYPES_H
+
+/* Define to 1 if you have the <unistd.h> header file. */
+#undef HAVE_UNISTD_H
+
+/* Define to the sub-directory in which libtool stores uninstalled libraries.
+   */
+#undef LT_OBJDIR
+
+/* Name of package */
+#undef PACKAGE
+
+/* Define to the address where bug reports for this package should be sent. */
+#undef PACKAGE_BUGREPORT
+
+/* Define to the full name of this package. */
+#undef PACKAGE_NAME
+
+/* Define to the full name and version of this package. */
+#undef PACKAGE_STRING
+
+/* Define to the one symbol short name of this package. */
+#undef PACKAGE_TARNAME
+
+/* Define to the home page for this package. */
+#undef PACKAGE_URL
+
+/* Define to the version of this package. */
+#undef PACKAGE_VERSION
+
+/* Define to 1 if you have the ANSI C header files. */
+#undef STDC_HEADERS
+
+/* Version number of package */
+#undef VERSION

configure.ac

+dnl
+dnl This file was autogenerated from "configure.ac.in".
+dnl Edit that file instead!
+dnl
+
+dnl configure.ac
+dnl
+dnl xfce4-mpc-plugin - mpd client plugin for the XFce4 panel
+dnl
+
+m4_define([mpc_version_major], [0])
+m4_define([mpc_version_minor], [5])
+m4_define([mpc_version_micro], [1])
+m4_define([mpc_version_tag], []) # Leave empty for releases
+m4_define([mpc_version_build], [288ea75])
+m4_define([mpc_version], [mpc_version_major().mpc_version_minor().mpc_version_micro()ifelse(mpc_version_tag(), [], [], [mpc_version_tag()-mpc_version_build()])])
+
+AC_INIT([xfce4-mpc-plugin], [mpc_version],
+	[landry@xfce.org])
+
+MPC_VERSION=mpc_version()
+AM_INIT_AUTOMAKE([1.8 dist-bzip2 tar-ustar no-dist-gzip])
+AM_CONFIG_HEADER([config.h])
+dnl AC_CONFIG_HEADERS([config.h])
+
+AM_MAINTAINER_MODE
+
+dnl Check for basic programs
+AC_PROG_CC
+AC_PROG_INSTALL
+IT_PROG_INTLTOOL([0.35.0])
+
+dnl Initialize libtool
+LT_PREREQ([2.2.6])
+LT_INIT([disable-static])
+
+dnl Check for standard header files
+AC_HEADER_STDC
+
+dnl configure the panel plugin
+XDT_CHECK_PACKAGE([LIBXFCE4PANEL], [libxfce4panel-2.0], [4.12.0])
+XDT_CHECK_PACKAGE([LIBXFCE4UI], [libxfce4ui-2], [4.12.0])
+
+dnl check for libmpd presence
+AC_ARG_WITH(libmpd,
+    AC_HELP_STRING([--with-libmpd=path], [path to libmpd base directory]),
+        LIBMPD_PATH="$withval", LIBMPD_PATH="")
+
+use_libmpd=false
+AM_CONDITIONAL([HAVE_LIBMPD], [test "$use_libmpd" = true])
+AC_DEFINE([HAVE_LIBMPD], [0], [no libmpd found])
+
+AC_MSG_CHECKING([whether --with-libmpd was used])
+if test x"$LIBMPD_PATH" != x"" ; then
+   if test x"$LIBMPD_PATH" = x"no" ; then
+      AC_MSG_RESULT([yes, disabled])
+      echo "* Build with libmpd: no, falling back to our implementation"
+   else
+      AC_MSG_RESULT([yes, using $LIBMPD_PATH])
+      LIBMPD_CFLAGS="-I${LIBMPD_PATH}/include/"
+      LIBMPD_LIBS="-L${LIBMPD_PATH}/lib/ -lmpd"
+      AC_DEFINE([HAVE_LIBMPD], [1], [libmpd found])
+      use_libmpd=true
+      AC_SUBST([LIBMPD_CFLAGS])
+      AC_SUBST([LIBMPD_LIBS])
+   fi
+else
+   AC_MSG_RESULT([no, falling back to pkg-config])
+   XDT_CHECK_OPTIONAL_PACKAGE([LIBMPD], [libmpd], [0.12], [libmpd], [libmpd])
+   if test x"$LIBMPD_FOUND" = x"yes"; then
+      AC_DEFINE([HAVE_LIBMPD], [1], [libmpd found])
+      use_libmpd=true
+      echo "* Build with libmpd: yes"
+   else
+      echo "* Build with libmpd: no, falling back to our implementation"
+   fi
+fi
+AM_CONDITIONAL(USE_LIBMPD, [test "$use_libmpd" = true])
+dnl Translations
+XDT_I18N([ar ast be bg ca cs da de el en_AU en_GB es eu fr gl he hr hu id is it ja ko lt lv ms nb nl oc pl pt pt_BR ru sk sq sr sv th tr ug uk ur ur_PK zh_CN zh_TW ])
+
+dnl Check for debugging support
+XDT_FEATURE_DEBUG()
+AC_OUTPUT([
+Makefile
+panel-plugin/Makefile
+po/Makefile.in
+])
+

debian/changelog

-xfce4-mpc-plugin (0.5.0-2) UNRELEASED; urgency=medium
+xfce4-mpc-plugin (0.5.1-1) unstable; urgency=medium
 
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-xfce@lists.debian.org
-
- -- Yves-Alexis Perez <corsac@debian.org>  Tue, 11 Dec 2018 21:13:21 +0100
+                                                                closes: #899874
+  * d/gbp.conf added, following DEP-14
+  * run wrap-and-sort
+  * d/watch: use HTTPS protocol
+  * New upstream version 0.5.1
+  * d/control: drop Lionel from uploaders, thanks!
+  * d/control: update standards version to 4.2.1
+  * d/control: use HTTPS protocol for Homepage
+  * update debhelper compat to 10
+
+ -- Yves-Alexis Perez <corsac@debian.org>  Tue, 11 Dec 2018 21:35:51 +0100
 
 xfce4-mpc-plugin (0.5.0-1) unstable; urgency=medium
 

debian/compat

-9
+10

debian/control

@@ -2,18 +2,24 @@ Source: xfce4-mpc-plugin
 Section: xfce
 Priority: optional
 Maintainer: Debian Xfce Maintainers <debian-xfce@lists.debian.org>
-Uploaders: Yves-Alexis Perez <corsac@debian.org>, Lionel Le Folgoc <mrpouit@gmail.com>
-Build-Depends: debhelper (>= 9), libxfce4panel-2.0-dev, libexo-1-dev,
- libxml-parser-perl, intltool, libxfce4ui-2-dev, autotools-dev,
- xfce4-dev-tools, automake, libtool
-Standards-Version: 3.9.8
-Homepage: http://goodies.xfce.org/projects/panel-plugins/xfce4-mpc-plugin/
+Uploaders: Yves-Alexis Perez <corsac@debian.org>
+Build-Depends: automake,
+               debhelper (>= 10),
+               intltool,
+               libexo-1-dev,
+               libtool,
+               libxfce4panel-2.0-dev,
+               libxfce4ui-2-dev,
+               libxml-parser-perl,
+               xfce4-dev-tools
+Standards-Version: 4.2.1
+Homepage: https://goodies.xfce.org/projects/panel-plugins/xfce4-mpc-plugin/
 Vcs-Git: https://salsa.debian.org/xfce-team/goodies/xfce4-mpc-plugin.git
 Vcs-Browser: https://salsa.debian.org/xfce-team/goodies/xfce4-mpc-plugin
 
 Package: xfce4-mpc-plugin
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}
 Suggests: mpd
 Description: Xfce panel plugin which serves as client for MPD music player
  This is a client for MPD music player which is added into a Xfce panel as a

debian/copyright

@@ -3,7 +3,7 @@ Thu, 26 Oct 2006 21:58:29 +0200
 
 It was downloaded from http://goodies.xfce.org/projects/panel-plugins/xfce4-mpc-plugin/
 
-Copyright Holders: 
+Copyright Holders:
 © 2006-2008 Landry Breuil <landry@fr.homeunix.org> / <gaston@gcu.info>
 
 License: