Hello community,

here is the log from the commit of package rubygem-inifile for openSUSE:Factory 
checked in at 2012-09-23 17:08:54
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/rubygem-inifile (Old)
 and      /work/SRC/openSUSE:Factory/.rubygem-inifile.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "rubygem-inifile", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/rubygem-inifile/rubygem-inifile.changes  
2011-11-28 18:27:56.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.rubygem-inifile.new/rubygem-inifile.changes     
2012-09-23 17:08:56.000000000 +0200
@@ -1,0 +2,10 @@
+Thu Aug 30 05:42:56 UTC 2012 - [email protected]
+
+- updated to version 2.0.0
+
+-------------------------------------------------------------------
+Wed Aug  1 05:04:39 UTC 2012 - [email protected]
+
+- updated to version 1.1.0
+
+-------------------------------------------------------------------

Old:
----
  inifile-0.4.0.gem

New:
----
  inifile-2.0.0.gem

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ rubygem-inifile.spec ++++++
--- /var/tmp/diff_new_pack.CGvWHc/_old  2012-09-23 17:08:57.000000000 +0200
+++ /var/tmp/diff_new_pack.CGvWHc/_new  2012-09-23 17:08:57.000000000 +0200
@@ -1,7 +1,7 @@
 #
 # spec file for package rubygem-inifile
 #
-# Copyright (c) 2011 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2012 SUSE LINUX Products GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -15,80 +15,95 @@
 # Please submit bugfixes or comments via http://bugs.opensuse.org/
 #
 
-# norootforbuild
+
 Name:           rubygem-inifile
-Version:        0.4.0
+Version:        2.0.0
 Release:        0
 %define mod_name inifile
-#
-Group:          Development/Languages/Ruby
-License:        MIT
-#
+%define mod_full_name %{mod_name}-%{version}
+
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
-BuildRequires:  rubygems_with_buildroot_patch
-%rubygems_requires
-#
-Url:            http://gemcutter.org/gems/inifile
-Source:         %{mod_name}-%{version}.gem
-#
+BuildRequires:  ruby-macros >= 1
+BuildRequires:  rubygem(rdoc) > 3.10
+Url:            http://rubygems.org/gems/inifile
+Source:         %{mod_full_name}.gem
 Summary:        INI file reader and writer
-%description
-This is a native Ruby package for reading and writing INI files.
+License:        MIT
+Group:          Development/Languages/Ruby
 
+%description
 Although made popular by Windows, INI files can be used on any system thanks
 to their flexibility. They allow a program to store configuration data, which
 can then be easily parsed and changed. Two notable systems that use the INI
 format are Samba and Trac.
-
-An initialization file, or INI file, is a configuration file that contains
-configuration data for Microsoft Windows based applications. Starting with
-Windows 95, the INI file format was superseded but not entirely replaced by
-a registry database in Microsoft operating systems.
-
-Although made popular by Windows, INI files can be used on any system thanks
-to their flexibility. They allow a program to store configuration data, which
-can then be easily parsed and changed.
+More information about INI files can be found on the [Wikipedia
+Page](http://en.wikipedia.org/wiki/INI_file).
+### Properties
+The basic element contained in an INI file is the property. Every property has
+a name and a value, delimited by an equals sign *=*. The name appears to the
+left of the equals sign and the value to the right.
+name=value
+### Sections
+Section declarations start with *[* and end with *]* as in `[section1]` and
+`[section2]` shown in the example below. The section declaration marks the
+beginning of a section. All properties after the section declaration will be
+associated with that section.
+### Comments
+All lines beginning with a semicolon *;* or a number sign *#* are considered
+to be comments. Comment lines are ignored when parsing INI files.
+### Example File Format
+A typical INI file might look like this:
+[section1]
+; some comment on section1
+var1 = foo
+var2 = doodle
+var3 = multiline values \
+are also possible
+[section2]
+# another comment
+var1 = baz
+var2 = shoodle
 
 %package doc
 Summary:        RDoc documentation for %{mod_name}
 Group:          Development/Languages/Ruby
-License:        MIT
 Requires:       %{name} = %{version}
+
 %description doc
 Documentation generated at gem installation time.
 Usually in RDoc and RI formats.
 
-
 %package testsuite
 Summary:        Test suite for %{mod_name}
 Group:          Development/Languages/Ruby
-License:        MIT
 Requires:       %{name} = %{version}
+
 %description testsuite
 Test::Unit or RSpec files, useful for developers.
 
-
 %prep
+#gem_unpack
+#if you need patches, apply them here and replace the # with a % sign in the 
surrounding lines
+#gem_build
+
 %build
-%install
-%gem_install %{S:0}
 
-%clean
-%{__rm} -rf %{buildroot}
+%install
+%gem_install -f
 
 %files
 %defattr(-,root,root,-)
-%{_libdir}/ruby/gems/%{rb_ver}/cache/%{mod_name}-%{version}.gem
-%{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_name}-%{version}/
-%exclude %{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_name}-%{version}/test
-%{_libdir}/ruby/gems/%{rb_ver}/specifications/%{mod_name}-%{version}.gemspec
+%{_libdir}/ruby/gems/%{rb_ver}/cache/%{mod_full_name}.gem
+%{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_full_name}/
+%exclude %{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_full_name}/test
+%{_libdir}/ruby/gems/%{rb_ver}/specifications/%{mod_full_name}.gemspec
 
 %files doc
 %defattr(-,root,root,-)
-%doc %{_libdir}/ruby/gems/%{rb_ver}/doc/%{mod_name}-%{version}/
+%doc %{_libdir}/ruby/gems/%{rb_ver}/doc/%{mod_full_name}/
 
 %files testsuite
 %defattr(-,root,root,-)
-%{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_name}-%{version}/test
+%{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_full_name}/test
 
 %changelog

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to