# packages

pkgId: 0d642fbac851bf78d26602aa357f751d523708a4474a604b420f3752e5ffbc86
name: bluez
arch: src
version: 5.29
epoch: 0
release: 1.fc21
summary: Bluetooth utilities
url: http://www.bluez.org/
rpm_license: GPLv2+
rpm_vendor: Fedora Project COPR (neyuki/origin)
rpm_group: Applications/System
rpm_buildhost: i-00037c9b
location_href: fedora-21-x86_64/bluez-5.29-1.fc21/bluez-5.29-1.fc21.src.rpm
checksum_type: sha256
description:
  Utilities for use in Bluetooth applications:
  	- hcitool
  	- hciattach
  	- hciconfig
  	- bluetoothd
  	- l2ping
  	- rfcomm
  	- sdptool
  	- bccmd
  	- bluetoothctl
  	- btmon
  	- hcidump
  	- l2test
  	- rctest
  	- start scripts (Red Hat)
  	- pcmcia configuration files

  The BLUETOOTH trademarks are owned by Bluetooth SIG, Inc., U.S.A.


pkgId: b0443ad538ab63d204f9c6d040b5e17a974b3c5b391bddb6d4c9ae6c019ae8e5
name: bluez-debuginfo
arch: x86_64
version: 5.29
epoch: 0
release: 1.fc21
summary: Debug information for package bluez
url: http://www.bluez.org/
rpm_license: GPLv2+
rpm_vendor: Fedora Project COPR (neyuki/origin)
rpm_group: Development/Debug
rpm_buildhost: i-00037c9b
rpm_sourcerpm: bluez-5.29-1.fc21.src.rpm
location_href: fedora-21-x86_64/bluez-5.29-1.fc21/bluez-debuginfo-5.29-1.fc21.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package bluez.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 62e451505d16f059f5d6407effbdfb1f32e3b977c586ae4bc842216436fcf3d9
name: bluez-hid2hci
arch: x86_64
version: 5.29
epoch: 0
release: 1.fc21
summary: Put HID proxying bluetooth HCI's into HCI mode
url: http://www.bluez.org/
rpm_license: GPLv2+
rpm_vendor: Fedora Project COPR (neyuki/origin)
rpm_group: System Environment/Daemons
rpm_buildhost: i-00037c9b
rpm_sourcerpm: bluez-5.29-1.fc21.src.rpm
location_href: fedora-21-x86_64/bluez-5.29-1.fc21/bluez-hid2hci-5.29-1.fc21.x86_64.rpm
checksum_type: sha256
description:
  Most allinone PC's and bluetooth keyboard / mouse sets which include a
  bluetooth dongle, ship with a so called HID proxying bluetooth HCI.
  The HID proxying makes the keyboard / mouse show up as regular USB HID
  devices (after connecting using the connect button on the device + keyboard),
  which makes them work without requiring any manual configuration.

  The bluez-hid2hci package contains the hid2hci utility and udev rules to
  automatically switch supported Bluetooth devices into regular HCI mode.

  Install this package if you want to use the bluetooth function of the HCI
  with other bluetooth devices like for example a mobile phone.

  Note that after installing this package you will first need to pair your
  bluetooth keyboard and mouse with the bluetooth adapter before you can use
  them again. Since you cannot use your bluetooth keyboard and mouse until
  they are paired, this will require the use of a regular (wired) USB keyboard
  and mouse.


pkgId: 2cd3f185c0f8ab301917c22995d6f88e663466d1eafc523994cf6e42fcc6e0d7
name: gtk-xfce-engine-debuginfo
arch: x86_64
version: 3.2.0
epoch: 0
release: 1.fc21
summary: Debug information for package gtk-xfce-engine
url: http://www.xfce.org/
rpm_license: GPLv2+
rpm_vendor: Fedora Project COPR (neyuki/origin)
rpm_group: Development/Debug
rpm_buildhost: i-00037c94
rpm_sourcerpm: gtk-xfce-engine-3.2.0-1.fc21.src.rpm
location_href: fedora-21-x86_64/gtk-xfce-engine-3.2.0-1.fc21/gtk-xfce-engine-debuginfo-3.2.0-1.fc21.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package gtk-xfce-engine.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 5bbb34913cebef6ec981903db21ea8a7719d9a80354e938cee3c1505bfbc8279
name: gtk2
arch: src
version: 2.24.27
epoch: 0
release: 2.fc21
summary: The GIMP ToolKit (GTK+), a library for creating GUIs for X
url: http://www.gtk.org
rpm_license: LGPLv2+
rpm_vendor: Fedora Project COPR (neyuki/origin)
rpm_group: System Environment/Libraries
rpm_buildhost: i-00037cb7
location_href: fedora-21-x86_64/gtk2-2.24.27-2.fc21/gtk2-2.24.27-2.fc21.src.rpm
checksum_type: sha256
description:
  GTK+ is a multi-platform toolkit for creating graphical user
  interfaces. Offering a complete set of widgets, GTK+ is suitable for
  projects ranging from small one-off tools to complete application
  suites.


pkgId: dcb25832acc77e911a01f24bf18696e601a39b27db8eb868ad55dac8691ddc67
name: gtk2-debuginfo
arch: x86_64
version: 2.24.27
epoch: 0
release: 2.fc21
summary: Debug information for package gtk2
url: http://www.gtk.org
rpm_license: LGPLv2+
rpm_vendor: Fedora Project COPR (neyuki/origin)
rpm_group: Development/Debug
rpm_buildhost: i-00037cb7
rpm_sourcerpm: gtk2-2.24.27-2.fc21.src.rpm
location_href: fedora-21-x86_64/gtk2-2.24.27-2.fc21/gtk2-debuginfo-2.24.27-2.fc21.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package gtk2.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 76d0cf4839f10c25d8b2172d4783484aba7c8a5becf6f94767fded37dd62759f
name: gtk2-devel
arch: x86_64
version: 2.24.27
epoch: 0
release: 2.fc21
summary: Development files for GTK+
url: http://www.gtk.org
rpm_license: LGPLv2+
rpm_vendor: Fedora Project COPR (neyuki/origin)
rpm_group: Development/Libraries
rpm_buildhost: i-00037cb7
rpm_sourcerpm: gtk2-2.24.27-2.fc21.src.rpm
location_href: fedora-21-x86_64/gtk2-2.24.27-2.fc21/gtk2-devel-2.24.27-2.fc21.x86_64.rpm
checksum_type: sha256
description:
  This package contains the libraries and header files that are needed
  for writing applications with the GTK+ widget toolkit. If you plan
  to develop applications with GTK+, consider installing the gtk2-devel-docs
  package.


pkgId: 98af388f633815e50ff2f6e121e4a914bbf4c9119d5eb9acd6dc4cbe1e4b6085
name: py3status
arch: noarch
version: 2.4
epoch: 0
release: 1
summary: py3status is an extensible i3status wrapper written in python
url: https://github.com/ultrabug/py3status
rpm_license: BSD
rpm_vendor: Ultrabug <ultrabug@ultrabug.net>
rpm_group: Development/Libraries
rpm_buildhost: i-0003833f
rpm_sourcerpm: py3status-2.4-1.src.rpm
location_href: fedora-21-x86_64/py3status-2.4-1/py3status-2.4-1.noarch.rpm
checksum_type: sha256
description:
  *********
  py3status
  *********
  |version|

  .. |version| image:: https://pypip.in/version/py3status/badge.png

  **py3status** is an extensible i3status wrapper written in python.

  Using py3status, you can take control of your i3bar easily by:

  - using one of the availables modules shipped with py3status
  - writing your own modules and have their output displayed on your bar
  - handling click events on your i3bar and play with them in no time
  - seeing your clock tick every second whatever your i3status interval

  **No extra configuration file needed**, just install & enjoy !

  Documentation
  =============
  Up to date documentation:

  - `See the wiki <https://github.com/ultrabug/py3status/wiki>`_

  Learn how to easily **handle i3bar click events** directly from your i3status config:

  - `Handle click events directly from your i3status config <https://github.com/ultrabug/py3status/wiki/Handle-click-events-directly-from-your-i3status-config>`_

  Learn how to **extend your current i3status config** to easily interact with your i3bar:

  - `Load and order py3status modules directly from your current i3status config <https://github.com/ultrabug/py3status/wiki/Load-and-order-py3status-modules-directly-from-your-current-i3status-config>`_

  Learn how to write your own modules:

  - `Write your own modules <https://github.com/ultrabug/py3status/wiki/Write-your-own-modules>`_

  Get help or share your ideas on IRC:

  - channel **#py3status** on **FreeNode**

  Usage
  =====
  In your i3 config file, simply switch from *i3status* to *py3status* in your *status_command*:
  ::

      status_command py3status

  Usually you have your own i3status configuration, just point to it:
  ::

      status_command py3status -c ~/.i3/i3status.conf

  Available modules
  =================
  You can get a list and short description of all the available modules by using the CLI:
  ::

      $ py3status modules list


  To get more details about all the available modules and their configuration, use:
  ::

      $ py3status modules details

  All the modules shipped with py3status are present in the sources in the `py3status/modules <https://github.com/ultrabug/py3status/tree/master/py3status/modules>`_ folder.

  Most of them are **configurable directly from your current i3status.conf**, check them out to see all the configurable variables.

  Installation
  ============
  Pypi
  ----
  Using pip:
  ::

      $ pip install py3status

  NB: **Debian users** should use **pypi-install** from the *python-stdeb* package instead of pip.

  Gentoo Linux
  ------------
  Using emerge:
  ::

      $ sudo emerge -a py3status

  Arch Linux
  ----------
  Thanks to @waaaaargh, py3status is present in the Arch User Repository using this URL:
  ::

      https://aur.archlinux.org/packages/py3status-git/

  Fedora
  ------
  Using yum:
  ::

      $ yum install py3status

  Options
  =======
  You can see the help of py3status by issuing `py3status -h`:
  ::

      -h, --help            show this help message and exit
      -c I3STATUS_CONF, --config I3STATUS_CONF
                            path to i3status config file
      -d, --debug           be verbose in syslog
      -i INCLUDE_PATHS, --include INCLUDE_PATHS
                            include user-written modules from those directories
                            (default ~/.i3/py3status)
      -n INTERVAL, --interval INTERVAL
                            update interval in seconds (default 1 sec)
      -s, --standalone      standalone mode, do not use i3status
      -t CACHE_TIMEOUT, --timeout CACHE_TIMEOUT
                            default injection cache timeout in seconds (default 60
                            sec)
      -v, --version         show py3status version and exit

  Control
  =======
  Just like i3status, you can force an update of your i3bar by sending a SIGUSR1 signal to py3status.
  Note that this will also send a SIGUSR1 signal to i3status.
  ::

      killall -USR1 py3status


