On 2006-10-05 12:43:44 +0200, Martin Vuk wrote:
additionally ... if your ruby library is provided as gem, you should package it as gem. (see rubygem-* packages) mostlikely another gem will depend on it. so having it as rubygem-* rpm makes it possible to use it from gems and use it directly from other libraries/scripts. I agree. I don't think the library is used at the moment by other gems, but it might be in the future. The problem is that the gems don't install the binaries, initscripts and such. So now I have two
2006/10/4, Marcus Rueckert
: packages puppet.rpm which provides library and binaries for the client and puppet-server.rpm providing the server part
So what do you suggest? Should I split the library part in gemruby-puppet.rpm and daemons, binaries and other stuff to puppet.rpm and puppet-server.rpm?
packaging a gem like that is ... hard to impossible. than lets stick to the old way. :) darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org