Ruby 2.1.0
by Vít Ondruch
Hi Rubyists!
I have pushed .spec file for Ruby 2.1.0 preview1 into private-ruby-2.1
[1] branch of Ruby's dist-git repository and I'll be pushing there
further changes leading into Ruby 2.1.0 package for Fedora 21. However:
* ATM, it doesn't build in Koji unfortunately, since there seems to be
some deadlock in test suite. Nevertheless, it builds (almost) fine in
mock on my computer.
* preview1 ships with preview version of RubyGems 2.2 and RDoc 4.1.0
which produces nonconforming package names such as
"rubygems-2.2.0.preview.1-0.15.preview1.fc21.noarch.rpm". Since I expect
that final version will ship non-preview versions, I don't care much
about the names.
Please test the package if you like. Any feedback (and help/patches ;)
is welcome.
Thanks
Vít
[1] http://pkgs.fedoraproject.org/cgit/ruby.git/log/?h=private-ruby-2.1
9 years, 11 months
rubygems 2.1.9 on rawhide and F-20
by Mamoru TASAKA
Hello, all:
With a lot of help from Vít and test by Josef wrt gem2rpm, I am going
to update rubygems on rawhide and F-20 to 2.1.9. As far as I tested,
it seems to be going well. Please fetch and test it, thank you.
Note that on F-19 rubygems will stay with 2.0.x (currently 2.0.12)
and on F-18 1.8.x (currently 1.8.25 with patched).
Regards,
Mamoru
10 years, 1 month
Filtering automatic provides
by Vít Ondruch
Hi Rubyists,
Binary ruby- and rubygem- packages ships .so files. These .so files are
picked up by RPM's automatic Requires/Provides generater and they are
listed among provides, e.g.:
$ repoquery -q --provides rubygem-sqlite3
rubygem(sqlite3) = 1.3.5-4.fc19
rubygem-sqlite3 = 1.3.5-4.fc19
rubygem-sqlite3(x86-64) = 1.3.5-4.fc19
sqlite3_native.so()(64bit)
However, these .so files are not useful outside of Ruby world and they
might even conflict with some system library (although I don't have any
example at my hand currently). So I believe, we should filter out these
automatic provides, as is done in Perl for example. Therefore, since
F19, there are available %{?ruby_default_filter} and
%{?rubygems_default_filter} macros, which allow to filter out these
provides.
For your curiosity, this is their implementation:
%ruby_default_filter %{expand: \
%global __provides_exclude_from
%{?__provides_exclude_from:%{__provides_exclude_from}|}^(%{ruby_vendorarchdir}|%{ruby_sitearchdir})/.*\\\\.so$
\
}
%rubygems_default_filter %{expand: \
%global __provides_exclude_from
%{?__provides_exclude_from:%{__provides_exclude_from}|}^%{gem_extdir_mri}/.*\\\\.so$
\
}
If nobody objects, I am going to propose usage of these macros into Ruby
packaging guidelines [1].
Vít
[1]
https://fedoraproject.org/w/index.php?title=PackagingDrafts/Ruby&diff=351...
10 years, 2 months