I am trying to summarize the gems freezing tricky parts again, as it was not easy to explain the problem to darix. We don't have a single rpm .spec file and split the plugins in subpackages but have one .spec in the main rails app and one .spec per plugin. Imagine the building of one plugin. The source is unpacked, and the plugin dependent gems are installed in the build environment via rpm BuildRequires (the sames that are listed in init.rb in the plugin using config.gem directives). Same with the base rails app, which is a build require and found at build time via the Rails.parent hack. The spec file runs rake gems:unpack and uh oh!. Not only the gems of the plugin are unpacked but also the ones from the main rails app, which rails sees as "one tree". There are more possible problems. In the example above, the freezed gems would go to the main app vendor/gems directory. What happens if two plugins (or the base rails app) require the same gem? who is the one unpacking it? -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ 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