Some gems put the ext/ source directory inside the gem, causing 2 types of warning/errors: - the source .c files get inside the gem, causing rpmlint to complain - sometimes the library gets duplicated in ext and lib /usr/lib64/ruby/gems/1.8/gems/nokogiri-1.3.3/lib/nokogiri/nokogiri.so /usr/lib64/ruby/gems/1.8/gems/nokogiri-1.3.3/ext/nokogiri/nokogiri.so because it is build in one and installed in the other. The ext/ one is useless and ignored, but makes the buildid extractor dizzy when creating debuginfo packages. As all rpm gems contain: %gem_install %{S:0} %gem_cleanup Shouldn't %gem_cleanup do rm -rf %{buildroot}/%{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_name}-%{version}/ext ? (I am doing this in a couple of gems already) -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ruby+help@opensuse.org