AUTHORS

+Stefan Ott <stefan@desire.ch>
+Andre Lerche <a.lerche@gmx.net>
+Benedikt Meurer <benedikt.meurer@unix-ag.uni-siegen.de>
+Mike Massonnet <mmassonnet@xfce.org>

INSTALL

+Installation Instructions
+*************************
+
+Copyright (C) 1994-1996, 1999-2002, 2004-2011 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 commands `./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 bug.  Until the bug is fixed you can use this workaround:
+
+     CONFIG_SHELL=/bin/bash /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 =														\
+	icons														\
+	panel-plugin												\
+	po
+
+distclean-local:
+	rm -rf *.cache *~
+
+distuninstallcheck_listfiles = find . -type f -print | grep -v ./share/icons/hicolor/icon-theme.cache
+
+.PHONY: ChangeLog
+
+ChangeLog: Makefile
+	(GIT_DIR=$(top_srcdir)/.git git log > .changelog.tmp \
+	&& mv .changelog.tmp ChangeLog; rm -f .changelog.tmp) \
+	|| (touch ChangeLog; echo 'Git directory not found: installing possibly empty changelog.' >&2)
+
+dist-hook: ChangeLog
+
+EXTRA_DIST =													\
+	README														\
+	intltool-extract.in											\
+	intltool-merge.in											\
+	intltool-update.in
+
+DISTCLEANFILES =												\
+	intltool-extract											\
+	intltool-merge												\
+	intltool-update
+

NEWS

+20161101 (1.1.0):
+-----------------
+  * set progressbar minimal width/height to 4px so that it looks like with gtk+2
+
+20160605 (1.0.99):
+-----------------
+  * port to gtk+3/libxfce4ui-2/libxfce4panel-2.0
+
+20150303 (1.0.2):
+-----------------
+
+  * Properly resize image _and_ btn so that the image is not shrinked
+  * New translations: th, ms, bg, oc, is, sl, en_AU
+  * Updated translations: ast, de, es, fr, it, hr, nl, pl, tr, ug
+
+20120630 (1.0.1):
+-----------------
+
+    * Better compliance with panel plugin HIG
+    * Fix look on transparent/colored panels
+    * Added compatibility with xfce4-panel v.4.9.0+
+    * Fix config loading (bug #8821)
+    * Fix build on GNU/Hurd (Bug #7955 / #8820)
+    * Port to libxfce4ui (bug #8143)
+    * Build the plugin as a module
+
+20101215 (1.0.0):
+-----------------
+
+    * Translated to 11 new languages, for a total of 38
+    * Detect the file manager automatically
+    * Replace limits in MB to percents
+    * Update the build system
+
+20081122 (0.4.2):
+-----------------
+
+    * Reverse the fraction of the progress
+
+20080113 (0.4.1):
+-----------------
+
+    * Switch "Hide button" with "Display button" #3802
+    * Replace xfce_themed_icon with gtk_icon_theme
+    * Some GUI tweaks in the dialog
+    * Display natural numbers in MB
+    * Replace the label with a checkbox+label for the name
+    * Fix pixbuf size in size-changed callback
+
+20071025 (0.4.0):
+-----------------
+
+	* Release 0.4.0
+
+20071021 (0.3.99.2):
+--------------------
+
+	* Set default plugin icon to xfce4-fsguard-plugin-warning
+	* Rename the "progress bar" to "meter"
+	* Fix size of plugin and border around the GtkProgressBar
+	* Reworked option dialog
+
+20071005 (0.3.99.1):
+--------------------
+	* New options to display the free space in a text label and in a
+	  progress bar, and the possibility to hide the button in the panel
+	* Redefined the strings
+	* Bug fixes and code cleanup
+
+20060206 (0.3.0):
+-----------------
+	* Ported to xfce 4.4 by Jasper Huijsmans, thanks!
+
+20051011 (0.2.1):
+-----------------
+	* The icon is now properly centered when no label is given
+
+20040204:
+---------
+	* Now it's possible to add mountpoints with max 32 chars
+	  as requested by Stefan Misel
+
+20040109:
+---------
+	* Added Polish translation by Daniel Mroz
+
+20031124:
+---------
+	* Added Korean translation by David Choi
+
+20031122:
+---------
+	* Fixed memory leak
+
+20031112:
+---------
+	* New option to choose the filemanager for button1 click
+
+20031111:
+---------
+	* The label is now located below the icon in vertical mode.
+
+	* Tooltip and Messagebox show the size in GB if MB > 1024.
+	
+	* Make this work on Net/Free/OpenBSD as well. Currently only tested
+	  on NetBSD.

README

+ FSGuard
+=========
+
+The FSGuard panel plugin checks free space on a chosen mount point
+frequently and displays a message when a limit is reached.  There are
+two limits: a warning limit where only the icon changes, and an urgent
+limit that advise the user with a message.  The icon button can be
+clicked to open the chosen mount point.
+
+
+ Homepage
+----------
+
+http://goodies.xfce.org/projects/panel-plugins/xfce4-fsguard-plugin
+
+
+ Dependencies
+--------------
+
+* libgtk+2 2.6
+* libxfcegui4 4.4.0
+* libxfce4util 4.4.0
+* libxfce4panel 4.4.0
+
+ Install
+---------
+
+% tar xf xfce4-fsguard-plugin-<version>.tar.gz
+% ./configure
+% make
+% make install
+
+See the INSTALL file for more instructions.
+
+
+ Report bugs
+-------------
+You can report bugs and feature requests on http://bugzilla.xfce.org/.
+Select the product “Xfce Panel Plugins” and the component “fsguard”.
+
+Feature requests are always welcome.
+
+You can also join the Xfce Goodies mailing-list at this address:
+http://foo-projects.org/mailman/listinfo/goodies-dev.
+

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 `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
+
+/* Define if libX11 is available */
+#undef HAVE_LIBX11
+
+/* 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 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
+
+/* Define to 1 if the X Window System is missing or not being used. */
+#undef X_DISPLAY_MISSING

configure.ac

+dnl
+dnl This file was autogenerated from "configure.ac.in".
+dnl Edit that file instead!
+dnl
+
+dnl xfce4-fsguard-plugin - <Plugin for xfce4-panel>
+dnl
+dnl 2003 Benedikt Meurer <benedikt.meurer@unix-ag.uni-siegen.de>
+dnl 2007 Mike Massonnet <mmassonnet@gmail.com>
+dnl
+
+m4_define([xfce4_fsguard_plugin_version_major], [1])
+m4_define([xfce4_fsguard_plugin_version_minor], [1])
+m4_define([xfce4_fsguard_plugin_version_micro], [0])
+m4_define([xfce4_fsguard_plugin_version_nano], [])
+m4_define([xfce4_fsguard_plugin_version_build], [a349adf])
+m4_define([xfce4_fsguard_plugin_version_tag], []) # Leave empty for releases
+m4_define([xfce4_fsguard_plugin_version], [xfce4_fsguard_plugin_version_major().xfce4_fsguard_plugin_version_minor().xfce4_fsguard_plugin_version_micro()ifelse(xfce4_fsguard_plugin_version_nano(), [], [], [.xfce4_fsguard_plugin_version_nano()])ifelse(xfce4_fsguard_plugin_version_tag(), [git], [xfce4_fsguard_plugin_version_tag()-xfce4_fsguard_plugin_version_build()], [xfce4_fsguard_plugin_version_tag()])])
+
+
+AC_INIT([Free Space Checker], [xfce4_fsguard_plugin_version], [http://bugzilla.xfce.org/], [xfce4-fsguard-plugin],
+	[http://goodies.xfce.org/projects/panel-plugins/xfce4-fsguard-plugin])
+
+AM_INIT_AUTOMAKE([1.8 dist-bzip2 tar-ustar no-dist-gzip])
+AM_CONFIG_HEADER([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 Check for X11 installed
+XDT_CHECK_LIBX11_REQUIRE
+
+dnl configure the panel plugin
+XDT_CHECK_PACKAGE([LIBXFCE4UI], [libxfce4ui-2], [4.12.0])
+XDT_CHECK_PACKAGE([LIBXFCE4UTIL], [libxfce4util-1.0], [4.8.0])
+XDT_CHECK_PACKAGE([LIBXFCE4PANEL], [libxfce4panel-2.0], [4.12.0])
+
+dnl check for i18n support
+XDT_I18N([ar ast bg ca cs da de el en_AU en_GB es eu fi fr gl he hr hu id is it ja kk ko lt lv ms nb nl nn oc pa pl pt pt_BR ru sk sl sq sr sv th tr ug uk ur ur_PK vi zh_CN zh_TW ])
+
+dnl Check for debugging support
+XDT_FEATURE_DEBUG()
+
+AC_OUTPUT([
+Makefile
+icons/Makefile
+icons/48x48/Makefile
+icons/36x36/Makefile
+icons/32x32/Makefile
+icons/24x24/Makefile
+icons/22x22/Makefile
+icons/16x16/Makefile
+icons/scalable/Makefile
+panel-plugin/Makefile
+po/Makefile.in
+])

debian/changelog

-xfce4-fsguard-plugin (1.1.0-2) UNRELEASED; urgency=medium
+xfce4-fsguard-plugin (1.1.0-2) 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>  Sat, 15 Dec 2018 16:40:42 +0100
+                                                                closes: #899737
+  * d/gbp.conf added, following DEP-14
+  * d/watch: use HTTPS protocol
+  * New upstream version 1.1.0
+  * d/control: drop Lionel from uploaders, thanks!
+  * d/control: update standards version to 4.2.1
+  * d/control: use HTTPS protocol for homepage field
+  * d/control: drop gtk2 build-dep since it's now GTK-3
+  * update debhelper compat to 10
+
+ -- Yves-Alexis Perez <corsac@debian.org>  Sat, 15 Dec 2018 16:53:11 +0100
 
 xfce4-fsguard-plugin (1.1.0-1) unstable; urgency=medium
 

debian/compat

-9
+10