ruby-dbus 0.9.0 → 0.9.1

data/Rakefile

@@ -3,7 +3,6 @@ require 'rake'
 require 'fileutils'
 include FileUtils
 require 'tmpdir'
-require 'rake/rdoctask'
 require 'rake/testtask'
 
 desc 'Default: run tests in the proper environment'
@@ -47,10 +46,3 @@ task :package_git do |t|
     cp Dir.glob("#{temp}/*.gem"), "."
   end
 end
-
-Rake::RDocTask.new do |rd|
-  rd.rdoc_dir = 'doc/rdoc'
-  rd.rdoc_files.include("README", "lib/**/*.rb")
-#  rd.options << "--diagram"
-#  rd.options << "--all"
-end

data/VERSION

@@ -1 +1 @@
-0.9.0
+0.9.1

data/lib/dbus/bus.rb

@@ -735,17 +735,22 @@ module DBus
     end
 
     def address_from_file
-      f = File.new("/var/lib/dbus/machine-id")
-      machine_id = f.readline.chomp
-      f.close
-      display = ENV["DISPLAY"].gsub(/.*:([0-9]*).*/, '\1')
-      File.open(ENV["HOME"] + "/.dbus/session-bus/#{machine_id}-#{display}").each do |line|
+      # systemd uses /etc/machine-id
+      # traditional dbus uses /var/lib/dbus/machine-id
+      machine_id_path = Dir['{/etc,/var/lib/dbus}/machine-id'].first
+      return nil unless machine_id_path
+      machine_id = File.read(machine_id_path).chomp
+
+      display = ENV["DISPLAY"][/:(\d+)\.?/, 1]
+
+      bus_file_path = File.join(ENV["HOME"], "/.dbus/session-bus/#{machine_id}-#{display}")
+      return nil unless File.exists?(bus_file_path)
+
+      File.open(bus_file_path).each_line do |line|
         if line =~ /^DBUS_SESSION_BUS_ADDRESS=(.*)/
           return $1
         end
       end
-    rescue Errno::ENOENT
-      nil
     end
   end
 

data/ruby-dbus.gemspec

@@ -14,7 +14,5 @@ GEMSPEC = Gem::Specification.new do |s|
   s.homepage = "https://trac.luon.net/ruby-dbus"
   s.files = FileList["{doc,examples,lib,test}/**/*", "Rakefile", "ruby-dbus.gemspec", "VERSION"].to_a.sort
   s.require_path = "lib"
-  s.has_rdoc = true
-  s.extra_rdoc_files = ["COPYING", "README.md", "NEWS"]
   s.required_ruby_version = ">= 1.8.7"
 end

data/test/dbus-limited-session.conf

@@ -8,7 +8,7 @@
   <type>session</type>
 
   <listen>unix:tmpdir=/tmp</listen>
-  <listen>tcp:host=localhost,port=0,family=ipv4</listen>
+  <listen>tcp:host=127.0.0.1,port=0,family=ipv4</listen>
 
   <standard_session_servicedirs />
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ruby-dbus
 version: !ruby/object:Gem::Version
-  version: 0.9.0
+  version: 0.9.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,16 +9,13 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-11-06 00:00:00.000000000 Z
+date: 2013-04-23 00:00:00.000000000 Z
 dependencies: []
 description: Pure Ruby module for interaction with D-Bus IPC system
 email: ruby-dbus-devel@lists.luon.net
 executables: []
 extensions: []
-extra_rdoc_files:
-- COPYING
-- README.md
-- NEWS
+extra_rdoc_files: []
 files:
 - Rakefile
 - VERSION
@@ -81,9 +78,6 @@ files:
 - test/thread_safety_test.rb
 - test/type_test.rb
 - test/variant_test.rb
-- COPYING
-- README.md
-- NEWS
 homepage: https://trac.luon.net/ruby-dbus
 licenses:
 - LGPL v2.1
@@ -110,4 +104,4 @@ signing_key:
 specification_version: 3
 summary: Ruby module for interaction with D-Bus
 test_files: []
-has_rdoc: true
+has_rdoc: 

data/COPYING

@@ -1,504 +0,0 @@
-		  GNU LESSER GENERAL PUBLIC LICENSE
-		       Version 2.1, February 1999
-
- Copyright (C) 1991, 1999 Free Software Foundation, Inc.
- 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-[This is the first released version of the Lesser GPL.  It also counts
- as the successor of the GNU Library Public License, version 2, hence
- the version number 2.1.]
-
-			    Preamble
-
-  The licenses for most software are designed to take away your
-freedom to share and change it.  By contrast, the GNU General Public
-Licenses are intended to guarantee your freedom to share and change
-free software--to make sure the software is free for all its users.
-
-  This license, the Lesser General Public License, applies to some
-specially designated software packages--typically libraries--of the
-Free Software Foundation and other authors who decide to use it.  You
-can use it too, but we suggest you first think carefully about whether
-this license or the ordinary General Public License is the better
-strategy to use in any particular case, based on the explanations below.
-
-  When we speak of free software, we are referring to freedom of use,
-not price.  Our General Public Licenses are designed to make sure that
-you have the freedom to distribute copies of free software (and charge
-for this service if you wish); that you receive source code or can get
-it if you want it; that you can change the software and use pieces of
-it in new free programs; and that you are informed that you can do
-these things.
-
-  To protect your rights, we need to make restrictions that forbid
-distributors to deny you these rights or to ask you to surrender these
-rights.  These restrictions translate to certain responsibilities for
-you if you distribute copies of the library or if you modify it.
-
-  For example, if you distribute copies of the library, whether gratis
-or for a fee, you must give the recipients all the rights that we gave
-you.  You must make sure that they, too, receive or can get the source
-code.  If you link other code with the library, you must provide
-complete object files to the recipients, so that they can relink them
-with the library after making changes to the library and recompiling
-it.  And you must show them these terms so they know their rights.
-
-  We protect your rights with a two-step method: (1) we copyright the
-library, and (2) we offer you this license, which gives you legal
-permission to copy, distribute and/or modify the library.
-
-  To protect each distributor, we want to make it very clear that
-there is no warranty for the free library.  Also, if the library is
-modified by someone else and passed on, the recipients should know
-that what they have is not the original version, so that the original
-author's reputation will not be affected by problems that might be
-introduced by others.
-
-  Finally, software patents pose a constant threat to the existence of
-any free program.  We wish to make sure that a company cannot
-effectively restrict the users of a free program by obtaining a
-restrictive license from a patent holder.  Therefore, we insist that
-any patent license obtained for a version of the library must be
-consistent with the full freedom of use specified in this license.
-
-  Most GNU software, including some libraries, is covered by the
-ordinary GNU General Public License.  This license, the GNU Lesser
-General Public License, applies to certain designated libraries, and
-is quite different from the ordinary General Public License.  We use
-this license for certain libraries in order to permit linking those
-libraries into non-free programs.
-
-  When a program is linked with a library, whether statically or using
-a shared library, the combination of the two is legally speaking a
-combined work, a derivative of the original library.  The ordinary
-General Public License therefore permits such linking only if the
-entire combination fits its criteria of freedom.  The Lesser General
-Public License permits more lax criteria for linking other code with
-the library.
-
-  We call this license the "Lesser" General Public License because it
-does Less to protect the user's freedom than the ordinary General
-Public License.  It also provides other free software developers Less
-of an advantage over competing non-free programs.  These disadvantages
-are the reason we use the ordinary General Public License for many
-libraries.  However, the Lesser license provides advantages in certain
-special circumstances.
-
-  For example, on rare occasions, there may be a special need to
-encourage the widest possible use of a certain library, so that it becomes
-a de-facto standard.  To achieve this, non-free programs must be
-allowed to use the library.  A more frequent case is that a free
-library does the same job as widely used non-free libraries.  In this
-case, there is little to gain by limiting the free library to free
-software only, so we use the Lesser General Public License.
-
-  In other cases, permission to use a particular library in non-free
-programs enables a greater number of people to use a large body of
-free software.  For example, permission to use the GNU C Library in
-non-free programs enables many more people to use the whole GNU
-operating system, as well as its variant, the GNU/Linux operating
-system.
-
-  Although the Lesser General Public License is Less protective of the
-users' freedom, it does ensure that the user of a program that is
-linked with the Library has the freedom and the wherewithal to run
-that program using a modified version of the Library.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.  Pay close attention to the difference between a
-"work based on the library" and a "work that uses the library".  The
-former contains code derived from the library, whereas the latter must
-be combined with the library in order to run.
-
-		  GNU LESSER GENERAL PUBLIC LICENSE
-   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-  0. This License Agreement applies to any software library or other
-program which contains a notice placed by the copyright holder or
-other authorized party saying it may be distributed under the terms of
-this Lesser General Public License (also called "this License").
-Each licensee is addressed as "you".
-
-  A "library" means a collection of software functions and/or data
-prepared so as to be conveniently linked with application programs
-(which use some of those functions and data) to form executables.
-
-  The "Library", below, refers to any such software library or work
-which has been distributed under these terms.  A "work based on the
-Library" means either the Library or any derivative work under
-copyright law: that is to say, a work containing the Library or a
-portion of it, either verbatim or with modifications and/or translated
-straightforwardly into another language.  (Hereinafter, translation is
-included without limitation in the term "modification".)
-
-  "Source code" for a work means the preferred form of the work for
-making modifications to it.  For a library, complete source code means
-all the source code for all modules it contains, plus any associated
-interface definition files, plus the scripts used to control compilation
-and installation of the library.
-
-  Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope.  The act of
-running a program using the Library is not restricted, and output from
-such a program is covered only if its contents constitute a work based
-on the Library (independent of the use of the Library in a tool for
-writing it).  Whether that is true depends on what the Library does
-and what the program that uses the Library does.
-  
-  1. You may copy and distribute verbatim copies of the Library's
-complete source code as you receive it, in any medium, provided that
-you conspicuously and appropriately publish on each copy an
-appropriate copyright notice and disclaimer of warranty; keep intact
-all the notices that refer to this License and to the absence of any
-warranty; and distribute a copy of this License along with the
-Library.
-
-  You may charge a fee for the physical act of transferring a copy,
-and you may at your option offer warranty protection in exchange for a
-fee.
-
-  2. You may modify your copy or copies of the Library or any portion
-of it, thus forming a work based on the Library, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
-    a) The modified work must itself be a software library.
-
-    b) You must cause the files modified to carry prominent notices
-    stating that you changed the files and the date of any change.
-
-    c) You must cause the whole of the work to be licensed at no
-    charge to all third parties under the terms of this License.
-
-    d) If a facility in the modified Library refers to a function or a
-    table of data to be supplied by an application program that uses
-    the facility, other than as an argument passed when the facility
-    is invoked, then you must make a good faith effort to ensure that,
-    in the event an application does not supply such function or
-    table, the facility still operates, and performs whatever part of
-    its purpose remains meaningful.
-
-    (For example, a function in a library to compute square roots has
-    a purpose that is entirely well-defined independent of the
-    application.  Therefore, Subsection 2d requires that any
-    application-supplied function or table used by this function must
-    be optional: if the application does not supply it, the square
-    root function must still compute square roots.)
-
-These requirements apply to the modified work as a whole.  If
-identifiable sections of that work are not derived from the Library,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works.  But when you
-distribute the same sections as part of a whole which is a work based
-on the Library, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote
-it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Library.
-
-In addition, mere aggregation of another work not based on the Library
-with the Library (or with a work based on the Library) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
-  3. You may opt to apply the terms of the ordinary GNU General Public
-License instead of this License to a given copy of the Library.  To do
-this, you must alter all the notices that refer to this License, so
-that they refer to the ordinary GNU General Public License, version 2,
-instead of to this License.  (If a newer version than version 2 of the
-ordinary GNU General Public License has appeared, then you can specify
-that version instead if you wish.)  Do not make any other change in
-these notices.
-
-  Once this change is made in a given copy, it is irreversible for
-that copy, so the ordinary GNU General Public License applies to all
-subsequent copies and derivative works made from that copy.
-
-  This option is useful when you wish to copy part of the code of
-the Library into a program that is not a library.
-
-  4. You may copy and distribute the Library (or a portion or
-derivative of it, under Section 2) in object code or executable form
-under the terms of Sections 1 and 2 above provided that you accompany
-it with the complete corresponding machine-readable source code, which
-must be distributed under the terms of Sections 1 and 2 above on a
-medium customarily used for software interchange.
-
-  If distribution of object code is made by offering access to copy
-from a designated place, then offering equivalent access to copy the
-source code from the same place satisfies the requirement to
-distribute the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
-  5. A program that contains no derivative of any portion of the
-Library, but is designed to work with the Library by being compiled or
-linked with it, is called a "work that uses the Library".  Such a
-work, in isolation, is not a derivative work of the Library, and
-therefore falls outside the scope of this License.
-
-  However, linking a "work that uses the Library" with the Library
-creates an executable that is a derivative of the Library (because it
-contains portions of the Library), rather than a "work that uses the
-library".  The executable is therefore covered by this License.
-Section 6 states terms for distribution of such executables.
-
-  When a "work that uses the Library" uses material from a header file
-that is part of the Library, the object code for the work may be a
-derivative work of the Library even though the source code is not.
-Whether this is true is especially significant if the work can be
-linked without the Library, or if the work is itself a library.  The
-threshold for this to be true is not precisely defined by law.
-
-  If such an object file uses only numerical parameters, data
-structure layouts and accessors, and small macros and small inline
-functions (ten lines or less in length), then the use of the object
-file is unrestricted, regardless of whether it is legally a derivative
-work.  (Executables containing this object code plus portions of the
-Library will still fall under Section 6.)
-
-  Otherwise, if the work is a derivative of the Library, you may
-distribute the object code for the work under the terms of Section 6.
-Any executables containing that work also fall under Section 6,
-whether or not they are linked directly with the Library itself.
-
-  6. As an exception to the Sections above, you may also combine or
-link a "work that uses the Library" with the Library to produce a
-work containing portions of the Library, and distribute that work
-under terms of your choice, provided that the terms permit
-modification of the work for the customer's own use and reverse
-engineering for debugging such modifications.
-
-  You must give prominent notice with each copy of the work that the
-Library is used in it and that the Library and its use are covered by
-this License.  You must supply a copy of this License.  If the work
-during execution displays copyright notices, you must include the
-copyright notice for the Library among them, as well as a reference
-directing the user to the copy of this License.  Also, you must do one
-of these things:
-
-    a) Accompany the work with the complete corresponding
-    machine-readable source code for the Library including whatever
-    changes were used in the work (which must be distributed under
-    Sections 1 and 2 above); and, if the work is an executable linked
-    with the Library, with the complete machine-readable "work that
-    uses the Library", as object code and/or source code, so that the
-    user can modify the Library and then relink to produce a modified
-    executable containing the modified Library.  (It is understood
-    that the user who changes the contents of definitions files in the
-    Library will not necessarily be able to recompile the application
-    to use the modified definitions.)
-
-    b) Use a suitable shared library mechanism for linking with the
-    Library.  A suitable mechanism is one that (1) uses at run time a
-    copy of the library already present on the user's computer system,
-    rather than copying library functions into the executable, and (2)
-    will operate properly with a modified version of the library, if
-    the user installs one, as long as the modified version is
-    interface-compatible with the version that the work was made with.
-
-    c) Accompany the work with a written offer, valid for at
-    least three years, to give the same user the materials
-    specified in Subsection 6a, above, for a charge no more
-    than the cost of performing this distribution.
-
-    d) If distribution of the work is made by offering access to copy
-    from a designated place, offer equivalent access to copy the above
-    specified materials from the same place.
-
-    e) Verify that the user has already received a copy of these
-    materials or that you have already sent this user a copy.
-
-  For an executable, the required form of the "work that uses the
-Library" must include any data and utility programs needed for
-reproducing the executable from it.  However, as a special exception,
-the materials to be distributed need not include anything that is
-normally distributed (in either source or binary form) with the major
-components (compiler, kernel, and so on) of the operating system on
-which the executable runs, unless that component itself accompanies
-the executable.
-
-  It may happen that this requirement contradicts the license
-restrictions of other proprietary libraries that do not normally
-accompany the operating system.  Such a contradiction means you cannot
-use both them and the Library together in an executable that you
-distribute.
-
-  7. You may place library facilities that are a work based on the
-Library side-by-side in a single library together with other library
-facilities not covered by this License, and distribute such a combined
-library, provided that the separate distribution of the work based on
-the Library and of the other library facilities is otherwise
-permitted, and provided that you do these two things:
-
-    a) Accompany the combined library with a copy of the same work
-    based on the Library, uncombined with any other library
-    facilities.  This must be distributed under the terms of the
-    Sections above.
-
-    b) Give prominent notice with the combined library of the fact
-    that part of it is a work based on the Library, and explaining
-    where to find the accompanying uncombined form of the same work.
-
-  8. You may not copy, modify, sublicense, link with, or distribute
-the Library except as expressly provided under this License.  Any
-attempt otherwise to copy, modify, sublicense, link with, or
-distribute the Library is void, and will automatically terminate your
-rights under this License.  However, parties who have received copies,
-or rights, from you under this License will not have their licenses
-terminated so long as such parties remain in full compliance.
-
-  9. You are not required to accept this License, since you have not
-signed it.  However, nothing else grants you permission to modify or
-distribute the Library or its derivative works.  These actions are
-prohibited by law if you do not accept this License.  Therefore, by
-modifying or distributing the Library (or any work based on the
-Library), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Library or works based on it.
-
-  10. Each time you redistribute the Library (or any work based on the
-Library), the recipient automatically receives a license from the
-original licensor to copy, distribute, link with or modify the Library
-subject to these terms and conditions.  You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties with
-this License.
-
-  11. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Library at all.  For example, if a patent
-license would not permit royalty-free redistribution of the Library by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Library.
-
-If any portion of this section is held invalid or unenforceable under any
-particular circumstance, the balance of the section is intended to apply,
-and the section as a whole is intended to apply in other circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system which is
-implemented by public license practices.  Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
-  12. If the distribution and/or use of the Library is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Library under this License may add
-an explicit geographical distribution limitation excluding those countries,
-so that distribution is permitted only in or among countries not thus
-excluded.  In such case, this License incorporates the limitation as if
-written in the body of this License.
-
-  13. The Free Software Foundation may publish revised and/or new
-versions of the Lesser General Public License from time to time.
-Such new versions will be similar in spirit to the present version,
-but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number.  If the Library
-specifies a version number of this License which applies to it and
-"any later version", you have the option of following the terms and
-conditions either of that version or of any later version published by
-the Free Software Foundation.  If the Library does not specify a
-license version number, you may choose any version ever published by
-the Free Software Foundation.
-
-  14. If you wish to incorporate parts of the Library into other free
-programs whose distribution conditions are incompatible with these,
-write to the author to ask for permission.  For software which is
-copyrighted by the Free Software Foundation, write to the Free
-Software Foundation; we sometimes make exceptions for this.  Our
-decision will be guided by the two goals of preserving the free status
-of all derivatives of our free software and of promoting the sharing
-and reuse of software generally.
-
-			    NO WARRANTY
-
-  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
-WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
-EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
-OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
-KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
-LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
-THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
-WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
-AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
-FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
-CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
-RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
-FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
-SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
-DAMAGES.
-
-		     END OF TERMS AND CONDITIONS
-
-           How to Apply These Terms to Your New Libraries
-
-  If you develop a new library, and you want it to be of the greatest
-possible use to the public, we recommend making it free software that
-everyone can redistribute and change.  You can do so by permitting
-redistribution under these terms (or, alternatively, under the terms of the
-ordinary General Public License).
-
-  To apply these terms, attach the following notices to the library.  It is
-safest to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least the
-"copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the library's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This library is free software; you can redistribute it and/or
-    modify it under the terms of the GNU Lesser General Public
-    License as published by the Free Software Foundation; either
-    version 2.1 of the License, or (at your option) any later version.
-
-    This library 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
-    Lesser General Public License for more details.
-
-    You should have received a copy of the GNU Lesser General Public
-    License along with this library; if not, write to the Free Software
-    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
-
-Also add information on how to contact you by electronic and paper mail.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the library, if
-necessary.  Here is a sample; alter the names:
-
-  Yoyodyne, Inc., hereby disclaims all copyright interest in the
-  library `Frob' (a library for tweaking knobs) written by James Random Hacker.
-
-  <signature of Ty Coon>, 1 April 1990
-  Ty Coon, President of Vice
-
-That's all there is to it!
-
-

data/NEWS

@@ -1,210 +0,0 @@
-= Ruby D-Bus NEWS
-
-Note about bug numbers:
- Ticket#1 - https://trac.luon.net/ruby-dbus/ticket/1
- Issue#1  - http://github.com/mvidner/ruby-dbus/issues#issue/1
- bnc#1    - https://bugzilla.novell.com/show_bug.cgi?id=1
-
-== Ruby D-Bus 0.9.0 - 2012-11-06
-
-Features:
- * When calling methods, the interface can be left unspecified if unambiguous
-  (Damiano Stoffie)
- * YARD documentation, Reference.md
-
-Bug fixes:
- * Introspection attribute "direction" can be omitted
-   as allowed by the specification (Noah Meyerhans).
- * ProxyObjectInterface#on_signal no longer needs the "bus" parameter
-   (Issue#31, by Damiano Stoffie)
-
-== Ruby D-Bus 0.8.0 - 2012-09-20
-
-Features:
- * Add Anonymous authentication (Issue#27, by Walter Brebels).
- * Use Nokogiri for XML parsing when available (Issue#24, by Geoff Youngs).
-
-Bug fixes:
- * Use SCM_CREDS authentication only on FreeBSD, not on OpenBSD (Issue#21,
-   reported by Adde Nilsson).
- * Recognize signature "h" (UNIX_FD) used eg. by Upstart (Issue#23,
-   by Bernd Ahlers).
- * Find the session bus also via launchd, on OS X (Issue#20, reported
-   by Paul Sturgess).
-
-Other:
- * Now doing continuous integration with Travis:
-     http://travis-ci.org/#!/mvidner/ruby-dbus
-
-
-== Ruby D-Bus 0.7.2 - 2012-04-05
-
-A brown-paper-bag release.
-
-Bug fixes:
- * Fixed "undefined local variable or method `continue'" in
-   DBus::Main#run when a service becomes idle (by Ravil Bayramgalin)
-
-== Ruby D-Bus 0.7.1 - 2012-04-04
-
-Bug fixes:
- * Fixed calling asynchronous methods on the default interface (Issue#13,
-   by Eugene Korbut). 
- * Fixed Main#quit to really quit the loop (by Josef Reidinger)
- * Unbundled files from Active Support (by Bohuslav Kabrda)
-
-== Ruby D-Bus 0.7.0 - 2011-07-26
-
-Features:
- * Added ASystemBus and ASessionBus, non-singletons useful in tests
-   and threads.
-
-Bug fixes:
- * Fixed handling of multibyte strings (Issue#8, by Takayuki YAMAGUCHI).
- * Allow reopening of a dbus_interface declaration (Issue#9, by T. YAMAGUCHI).
- * Fixed ruby-1.9.2 compatibility again (Issue#12).
- * Fixed authentication on BSD (Issue#11, by Jonathan Walker)
- * Fixed exiting a nested event loop for synchronous calls
-   (reported by Timo Warns).
- * Fixed introspection calls leaking reply handlers.
- * "rake test" now works, doing what was called "rake env:test"
-
-== Ruby D-Bus 0.6.0 - 2010-12-11
-
-Features:
- * Clients can access properties conveniently (Ticket#28).
-
-Bug fixes:
- * Service won't crash whan handling an unknown method or interface (Ticket#31).
- * Don't send an invalid error name when it originates from a NameError.
-
-== Ruby D-Bus 0.5.0 - 2010-11-07
-
-Features:
- * Better binding of Ruby Exceptions to D-Bus Errors.
- * Converted the package to a Gem (Issue#6).
- * Converted the tutorial from Webgen to Markdown.
-
-Bug fixes:
- * Don't pass file descriptors to subprocesses.
- * Fixed InterfaceElement::validate_name (Ticket#38, by Herwin Weststrate).
- * Fixed a typo in InvalidDestinationName description (Ticket#40).
-
-== Ruby D-Bus 0.4.0 - 2010-08-20
-
-Features:
- * TCP transport (by pangdudu)
- * Enabled test code coverage report (rcov)
-
-Bug fixes:
- * Classes should not share all interfaces (Ticket#36/Issue#5)
- * Ruby 1.9 compatibility (Ticket#37, by Myra Nelson)
-
-== Ruby D-Bus 0.3.1 - 2010-07-22
-
-Bug fixes:
- * Many on_signal could cause DBus.Error.LimitsExceeded bnc#617350).
-   Don't add a match rule that already exists, enable removing match
-   rules. Now only one handler for a rule is called (but it is possible
-   for one signal to match more rules). This reverts the half-fix done
-   to fix Issue#3
- * Re-added InterfaceElement#add_param for compatibility.
- * Handle more ways which tell us that a bus connection has died.
-
-== Ruby D-Bus 0.3.0 - 2010-03-28
-
-Bug fixes:
- 
- * Fixed "undefined method `get_node' for nil:NilClass"
-   on Ubuntu Karmic (Ticket#34).
- * Get the session bus address even if unset in ENV (Issue#4).
- * Improved exceptions a bit:
-   UndefinedInterface, InvalidMethodName, NoMethodError, no RuntimeException
-
- These are by Klaus Kaempf:
- * Make the signal dispatcher call all handlers (Issue#3).
- * Run on Ruby < 1.8.7 (Issue#2).
- * Avoid needless DBus::IncompleteBufferException (Ticket#33).
- * Don't ignore DBus Errors in request_service, raise them (Ticket#32).
-
-Features:
-
- * Automatic signature inference for variants.
- * Introduced FormalParameter where a plain pair had been used.
-
-== Ruby D-Bus 0.2.12 - 2010-01-24
-
-Bug fixes:
-
- * Fixed a long-standing bug where a service activated by the bus
-   would fail with "undefined method `get_node' for nil:NilClass"
-   (Tickets#25 and #29).
-
-== Ruby D-Bus 0.2.11 - 2009-11-12
-
-Features:
-
- * Added DBus::Service#unexport (da1l6).
-
-Bug fixes:
-
- * Return org.freedesktop.DBus.Error.UnknownObject instead of crashing
-   (Ticket#31).
- * Rescue exceptions in dbus_methods and reply with DBus errors instead of
-   crashing (da1l6).
- * Better exception messages when sending nil, or mismatched structs.
- * Call mktemp without --tmpdir, to build on older distros.
-
-== Ruby D-Bus 0.2.10 - 2009-09-10
-
-Bug fixes:
-
- * DBus::Service.exists? fixed (Murat Demirten).
- * Ruby 1.9 fixes (Jedediah Smith).
- * Fixed an endless sleep in DBus::Main.run (bnc#537401).
- * Added details to PacketMarshaller exceptions (bnc#538050).
-
-(bnc#FOO refers to https://bugzilla.novell.com/show_bug.cgi?id=FOO )
-
-== Ruby D-Bus "I'm not dead" 0.2.9 - 2009-08-26
-
-Thank you to Paul and Arnaud for starting the project. I, Martin
-Vidner, am continuing with it on GitHub.
-
- * Fixed passing an array through a variant (no ticket).
- * Fixed marshalling "av" (Ticket #30).
- * Fixed variant alignment (Ticket #27).
- * Added DBus::Main.quit.
- * Mention the DBus interface in a NameError for an unknown method.
- * Fixed ruby-1.9 "warning: default `to_a' will be obsolete".
- * Added Rakefile and gemspec.
-
-== Ruby D-Bus "Thanks for all the fish" 0.2.1 - 2007-12-29
-
-More bugfixes, mostly supplied by users supplying us with patches.  Thanks!
-
- * Support for new types added: 
-   - dict (courtesy of Drake Wilson);
-   - double (courtesy of Patrick Sissons);
-   - variant.
- * Improved exception raise support (courtesy of Sjoerd Simons,
-   Patrick Sissons).
- * Some polish (removed debug output, solved unnecessary warnings).
- * Documentation updates, example fixes and updates.
-
-== Ruby D-Bus "Almost live from DebConf 7" 0.2.0 - 2007-06-02
-
-Again a bugfix release, also meant to be the public release
-for exploratory purposes. New in 0.2.0:
-
- * Complete tutorial revamp.
- * Relicensed to the LGPL.
-
-== Ruby D-Bus "Release Often" 0.1.1 - 2007-04-23
-
-Bugfix release.  Fixes hardcoded string for requesting bus names,
-found by Rudi Cilibrasi.
-
-== Ruby D-Bus "Happy Birthday Paul" 0.1.0 - 2007-04-17
-
-First release. Supports most of D-Bus' features.

data/README.md

@@ -1,42 +0,0 @@
-# Ruby D-Bus README
-
-Ruby D-Bus provides an implementation of the D-Bus protocol such that the
-D-Bus system can be used in the Ruby programming language.
-
-## Requirements
-
-- Ruby 1.8.7 or 1.9
-
-## Installation
-
-- `gem install ruby-dbus`
-
-## Features
-
-Ruby D-Bus currently supports the following features:
-
- * Connecting to local buses.
- * Accessing remote services, objects and interfaces.
- * Invoking methods on remote objects synchronously and asynchronously.
- * Catch signals on remote objects and handle them via callbacks.
- * Remote object introspection.
- * Walking object trees.
- * Creating services and registering them on the bus.
- * Exporting objects with interfaces on a bus for remote use.
- * Rubyish D-Bus object and interface syntax support that automatically
-   allows for introspection.
- * Emitting signals on exported objects.
-
-## Usage
-
- See some of the examples in the examples/ subdirectory of the tarball.
- Also, check out the included tutorial (in Markdown format) in doc/Tutorial.md
- or view it online on
- <https://github.com/mvidner/ruby-dbus/blob/master/doc/Tutorial.md> .
-
-## License
-
- Ruby D-Bus is free software; you can redistribute it and/or modify it
- under the terms of the GNU Lesser General Public License as published by the
- Free Software Foundation; either version 2.1 of the License, or (at
- your option) any later version.